CSRF in Jhumanj Opnform
CVE-2025-11442
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 class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.003, 21.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Jhumanj Opnform — versions 1.9.0, 1.9.1, 1.9.2
Weakness classification (CWE)
References
- VDB-327379 | JhumanJ OpnForm API Endpoint cross-site request forgery (Third Party Advisory, VDB Entry, vdb-entry)
- VDB-327379 | CTI Indicators (IOB, IOC) (signature, Permissions Required, permissions-required, VDB Entry)
- Submit #666889 | GitHub OpnForm 1.9.3 Cross-Site Request Forgery (Third Party Advisory, VDB Entry, third-party-advisory)
- docs.google.com/document/d/1GUjJA9vUbsXUngAv6ySsbCIhVynf8_djardLZYEDOe0/edit (Exploit, Third Party Advisory, exploit)