Data alteration via disputed API request forgery
Published Oct 8, 2025 · Updated Oct 8, 2025
Cross-site request forgery in OpnForm 1.9.0 through 1.9.3 allows attackers to alter data through an unspecified API endpoint. The public record does not identify the endpoint, request field, or server-side operation that accepts the forged request. OpnForm disputes classic CSRF reachability because API calls require an Authorization bearer token; an attacker must first obtain a JWT, so the published proof of concept does not provide initial access.
Summary
What happened
Cross-site request forgery in OpnForm 1.9.0 through 1.9.3 allows attackers to alter data through an unspecified API endpoint. The public record does not identify the endpoint, request field, or server-side operation that accepts the forged request. OpnForm disputes classic CSRF reachability because API calls require an Authorization bearer token; an attacker must first obtain a JWT, so the published proof of concept does not provide initial access.
The record
- CVE
- CVE-2025-11442
- Published
- Oct 8, 2025
- Updated
- Oct 8, 2025
- Vendor
- JhumanJ
- Product
- OpnForm
- Classifications
- CWE-862, CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 8, 2025CVE publishedPublication date reported by the CVE source.
- Oct 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.9.0
- Affected versionversion=1.9.1
- Affected versionversion=1.9.2
- Affected versionversion=1.9.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OpnForm API endpoint CSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo