{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5112 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5112 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5112 is a high-severity cross-site scripting vulnerability in Gravity Forms, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5112 and fix it if it is affected.\n\nWhat it is: CVE-2026-5112 is a high-severity cross-site scripting vulnerability in Gravity Forms, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5112 in the wild and no public exploit code.\n\nAffected product: Gravity 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-2026-5112/ (Markdown: https://insights.sbomify.com/CVE-2026-5112/index.md)","id":"CVE-2026-5112","markdown":"https://insights.sbomify.com/CVE-2026-5112/index.md","name":"CVE-2026-5112","record":{"aliases":["GHSA-2qgr-m7c7-j745"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject scripts via Gravity Forms calculation fields, executing code in admin browsers to potentially take over accounts.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Gravity Forms plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping of Calculation Product field product names when rendered inside Repeater fields. The validate() method in the GF_Field_Calculation class only validates the quantity field (.3) and completely ignores the product name field (.1), allowing malicious HTML to pass through validation. When the value is saved, the sanitize_entry_value() method returns the raw value without sanitization for fields where HTML is not expected. Subsequently, when an entry is viewed in wp-admin, the get_value_entry_detail() method concatenates the unescaped product name directly into the output string, which is then rendered by the repeater's get_value_entry_detail() method without further escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via form submissions that will execute whenever an authenticated administrator with the gravityforms_view_entries capability accesses the entry detail page.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Gravity Forms \u003c= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Calculation Product Field in Repeater","id":"CVE-2026-5112","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gravity Forms \u003c= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Consent Field Hidden Input","id":"CVE-2026-5113"},"packages":[],"prev":{"headline":"Gravity Forms \u003c= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Hidden Product Field in Repeater","id":"CVE-2026-5111"},"products":["Gravity Forms"],"published":"2026-05-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-04","vendors":["Gravity Forms"]},"summary":"Unauthenticated attackers can inject scripts via Gravity Forms calculation fields, executing code in admin browsers to potentially take over accounts.","url":"https://insights.sbomify.com/CVE-2026-5112/"}