{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4394 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4394 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4394 is a medium-severity cross-site scripting vulnerability in Gravity Forms, published on 7 Apr 2026. 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-2026-4394 and fix it if it is affected.\n\nWhat it is: CVE-2026-4394 is a medium-severity cross-site scripting vulnerability in Gravity Forms, published on 7 Apr 2026. 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-2026-4394 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-4394/ (Markdown: https://insights.sbomify.com/CVE-2026-4394/index.md)","id":"CVE-2026-4394","markdown":"https://insights.sbomify.com/CVE-2026-4394/index.md","name":"CVE-2026-4394","record":{"aliases":["GHSA-5pv5-mj98-fr8x"],"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 the Credit Card field, leading to code execution when administrators view entries.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Stored Cross-Site Scripting via the Credit Card field's 'Card Type' sub-field (`input_\u003cid\u003e.4`) in all versions up to, and including, 2.9.30. This is due to the `get_value_entry_detail()` method in the `GF_Field_CreditCard` class outputting the card type value without escaping, combined with `get_value_save_entry()` accepting and storing unsanitized user input for the `input_\u003cid\u003e.4` parameter. The Card Type field is not rendered on the frontend form (it is normally derived from the card number), but the backend submission parser blindly accepts it if included in the POST request. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form entry in the WordPress dashboard.","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.9.30 - Unauthenticated Stored Cross-Site Scripting via Credit Card 'Card Type' Sub-Field","id":"CVE-2026-4394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Heap-based buffer overflow in wc_ecc_import_x963_ex KCAPI path","id":"CVE-2026-4395"},"packages":[],"prev":{"headline":"Automated Logout - Moderately critical - Cross-site request forgery - SA-CONTRIB-2026-030","id":"CVE-2026-4393"},"products":["Gravity Forms"],"published":"2026-04-07","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["Gravity Forms"]},"summary":"Unauthenticated attackers can inject scripts via the Credit Card field, leading to code execution when administrators view entries.","url":"https://insights.sbomify.com/CVE-2026-4394/"}