{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31040 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31040 is a high-severity vulnerability in open-formulieren open-forms, published on 13 Jun 2022. 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-2022-31040 and fix it if it is affected.\n\nWhat it is: CVE-2022-31040 is a high-severity vulnerability in open-formulieren open-forms, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-31040 in the wild and no public exploit code.\n\nAffected product: open-formulieren open-forms. 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-2022-31040/ (Markdown: https://insights.sbomify.com/CVE-2022-31040/index.md)","id":"CVE-2022-31040","markdown":"https://insights.sbomify.com/CVE-2022-31040/index.md","name":"CVE-2022-31040","record":{"aliases":["GHSA-c97h-m5qf-j8mf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Open Forms application","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via an unvalidated referer parameter in the cookie consent page, facilitating phishing attacks.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"open_forms","vendor":"maykinmedia"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Open Forms is an application for creating and publishing smart forms. Prior to versions 1.0.9 and 1.1.1, the cookie consent page in Open Forms contains an open redirect by injecting a `referer` querystring parameter and failing to validate the value. A malicious actor is able to redirect users to a website under their control, opening them up for phishing attacks. The redirect is initiated by the open forms backend which is a legimate page, making it less obvious to end users they are being redirected to a malicious website. Versions 1.0.9 and 1.1.1 contain patches for this issue. There are no known workarounds avaialble.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Open Redirect in open-forms","id":"CVE-2022-31040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Insufficient content-type validation for uploaded files in open-forms","id":"CVE-2022-31041"},"packages":[],"prev":{"headline":"Improper privilege management - Anyone can view room settings in GreenLight","id":"CVE-2022-31039"},"products":["open-forms"],"published":"2022-06-13","related":[{"cvss_score":7.7,"headline":"Open Forms potential multi-factor authentication bypass","id":"CVE-2024-24771","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":7.6,"headline":"Insufficient content-type validation for uploaded files in open-forms","id":"CVE-2022-31041","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":6.5,"headline":"Open Forms possible to view submission details of other people than intended","id":"CVE-2026-28803","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":4.3,"headline":"Open Forms prefill data in read-only components can be tampered","id":"CVE-2025-64515","kev_date_added":null,"published":"2025-11-18"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["open-formulieren"]},"summary":"Attackers can redirect users to malicious sites via an unvalidated referer parameter in the cookie consent page, facilitating phishing attacks.","url":"https://insights.sbomify.com/CVE-2022-31040/"}