{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5110 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-5110 and fix it if it is affected.\n\nWhat it is: CVE-2026-5110 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-5110 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-5110/ (Markdown: https://insights.sbomify.com/CVE-2026-5110/index.md)","id":"CVE-2026-5110","markdown":"https://insights.sbomify.com/CVE-2026-5110/index.md","name":"CVE-2026-5110","record":{"aliases":["GHSA-gc9j-26wq-g797"],"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 malicious scripts via product fields, leading to code execution in administrator browsers.","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 in the SingleProduct field when used inside a Repeater field. When SingleProduct fields are nested within Repeater fields, the validation flow bypasses the state validation mechanism (failed_state_validation()) that would normally prevent tampering with field values. The validate_subfield() method only calls the field's validate() method, which for SingleProduct fields only validates the quantity field and does not check the product name field for tampering. As a result, an attacker can inject arbitrary HTML and JavaScript into the product name field (input .1). This malicious input is then saved to the database without sanitization because sanitize_entry_value() returns raw values when HTML is not expected for the field type. When an administrator views the entry in wp-admin/admin.php?page=gf_entries, the get_value_entry_detail() method outputs the product name without escaping, causing the stored XSS payload to execute in the administrator's browser. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses an entry containing the malicious payload.","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 Single Product Field Inside Repeater","id":"CVE-2026-5110","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 Hidden Product Field in Repeater","id":"CVE-2026-5111"},"packages":[],"prev":{"headline":"Gravity Forms \u003c= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Product Option","id":"CVE-2026-5109"},"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 malicious scripts via product fields, leading to code execution in administrator browsers.","url":"https://insights.sbomify.com/CVE-2026-5110/"}