CVE-2025-11442
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
A security flaw has been discovered in JhumanJ OpnForm up to 1.9.3. The impacted element is an unknown function of the component API Endpoint. The manipulation results in cross-site request forgery. The attack may be performed from remote. The exploit has been released to the public and may be exploited. The vendor has stated that API calls require authentication through Authorization Bearer Tokens, so classic CSRF attacks do not apply here. An attacker would need to possess the JWT through means such as XSS which were mitigated, disabling any form of initial access.
Risk Assessment
Despite the vendor's claims of limited risk, a publicly available exploit could be used in specific scenarios if an attacker obtains a JWT.
Recommendation
Update JhumanJ OpnForm to the latest version and ensure API authentication mechanisms and XSS protections are properly implemented.
Other vulnerabilities in JhumanJ OpnForm
See all- CVE-2025-11440Medium
A vulnerability in JhumanJ OpnForm up to 1.9.3 involves improper access controls in /edit. The attack can be executed remotely. The exploit is publicly disclosed. A patch is recommended: b15e29021d326be127193a5dbbd528c4e37e6324.
- CVE-2025-11439Medium
A vulnerability in JhumanJ OpnForm up to 1.9.3 involves missing authorization in /show/integrations. The attack can be executed remotely. The exploit is publicly disclosed. A patch is recommended: 11d97d78f2de2cb49f79baed6bde8b611ec1f384.
- CVE-2025-11438Medium
A vulnerability has been found in JhumanJ OpnForm up to 1.9.3 affecting /custom-domains in the API Endpoint component. Manipulation leads to missing authorization. The attack may be launched remotely and the exploit is public. The patch name is beb153ce52dceb971c1518f98333328c95f1ba20.
Original NVD description (English source)
A security flaw has been discovered in JhumanJ OpnForm up to 1.9.3. The impacted element is an unknown function of the component API Endpoint. The manipulation results in cross-site request forgery. The attack may be performed from remote. The exploit has been released to the public and may be exploited. The vendor has stated that API calls require authentication through Authorization Bearer Tokens, so classic CSRF attacks do not apply here. An attacker would need to possess the JWT through means such as XSS which were mitigated, disabling any form of initial access.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS