{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11442 exists.","fix":"No fix has been published for CVE-2025-11442 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11442 is a medium-severity vulnerability in JhumanJ OpnForm, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-11442 and fix it if it is affected.\n\nWhat it is: CVE-2025-11442 is a medium-severity vulnerability in JhumanJ OpnForm, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11442 exists.\n\nAffected product: JhumanJ OpnForm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-11442/ (Markdown: https://insights.sbomify.com/CVE-2025-11442/index.md)","id":"CVE-2025-11442","markdown":"https://insights.sbomify.com/CVE-2025-11442/index.md","name":"CVE-2025-11442","record":{"aliases":["GHSA-2xc4-fqpw-rrgw"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpnForm web application","requires_auth":"none","summary":"A cross-site request forgery vulnerability in OpnForm's API endpoint, though vendor claims authentication mitigates classic CSRF risks.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"opnform","vendor":"jhumanj"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"JhumanJ OpnForm API Endpoint cross-site request forgery","id":"CVE-2025-11442","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"JhumanJ OpnForm Forgotten Password email information exposure","id":"CVE-2025-11443"},"packages":[],"prev":{"headline":"JhumanJ OpnForm HTTP Header excessive authentication","id":"CVE-2025-11441"},"products":["OpnForm"],"published":"2025-10-08","related":[{"cvss_score":6.3,"headline":"JhumanJ OpnForm HTTP Header excessive authentication","id":"CVE-2025-11441","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":6.3,"headline":"JhumanJ OpnForm Forgotten Password email information exposure","id":"CVE-2025-11443","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"JhumanJ OpnForm submissions cross site scripting","id":"CVE-2025-11435","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"JhumanJ OpnForm answer unrestricted upload","id":"CVE-2025-11436","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"JhumanJ OpnForm API Endpoint custom-domains authorization","id":"CVE-2025-11438","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"JhumanJ OpnForm integrations authorization","id":"CVE-2025-11439","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"JhumanJ OpnForm edit access control","id":"CVE-2025-11440","kev_date_added":null,"published":"2025-10-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-08","vendors":["JhumanJ"]},"summary":"A cross-site request forgery vulnerability in OpnForm's API endpoint, though vendor claims authentication mitigates classic CSRF risks.","url":"https://insights.sbomify.com/CVE-2025-11442/"}