CVE-2026-4394
Stored XSS in Gravity Forms Credit Card Field Allows Admin Attack
Publication date: 2026-04-08
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rocketgenius | gravity_forms | to 2.9.30 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Gravity Forms plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the Credit Card field's 'Card Type' sub-field (input_<id>.4) in all versions up to and including 2.9.30.
This occurs because the method get_value_entry_detail() in the GF_Field_CreditCard class outputs the card type value without escaping it, and get_value_save_entry() accepts and stores unsanitized user input for this parameter.
Although the Card Type field is not shown on the frontend form (it is normally derived from the card number), the backend submission parser accepts it if included in a POST request.
This allows unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form entry in the WordPress dashboard.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to execute arbitrary scripts in the context of the WordPress dashboard when an administrator views a maliciously crafted form entry.
Such script execution can lead to compromise of administrator accounts, theft of sensitive information, or further attacks on the WordPress site.
Because the attack requires only a specially crafted POST request and no authentication, it poses a significant risk to site security.