dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4394

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Credit Card field's 'Card Type' sub-field (`input_<id>.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_<id>.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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Gravity Forms plugin for WordPress contains a stored XSS vulnerability in the Credit Card field's Card Type sub-field (input_<id>.4). The get_value_save_entry() method accepts and stores unsanitized user input from POST requests, and get_value_entry_detail() outputs this value without escaping when administrators view form entries in the dashboard.

MitigationUpdate Gravity Forms to version 2.9.31 or later which contains the fix for proper input sanitization and output escaping. If immediate update is not possible, restrict access to form entry dashboards or disable the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Gravity Forms plugin is installed
    Navigate to WordPress admin > Plugins or check wp-content/plugins/ for 'gravityforms' directory. Alternatively, search for 'Gravity Forms' in the Plugins page.
    Affected if Plugin is not installed or not present in the system
  2. Check installed Gravity Forms version
    Go to WordPress admin > Plugins > Gravity Forms and look at the version number, or check the main plugin file header for 'Version:' value. Compare against 2.9.31.
    Affected if Version is lower than 2.9.31 (e.g., 2.9.30, 2.9.0, 2.8.x, etc.)
  3. Identify forms using Credit Card fields
    Go to Forms > Forms in WordPress admin. For each form, edit it and look for a 'Credit Card' field type in the form editor. Note the field IDs.
    Affected if At least one form contains an active Credit Card field
  4. Inspect recent POST submissions for suspicious input
    Check server access logs or web application firewall logs for POST requests to /?gf_page=submit or /wp-json/gf/v2/submissions containing patterns like 'input_<number>.4=' with unusual characters such as <script, javascript:, or encoded HTML tags.
    Affected if POST requests to Gravity Forms endpoints contain unsanitized Card Type values (input_<id>.4 parameter)

The environment is affected if Gravity Forms version is below 2.9.31 AND at least one form contains an active Credit Card field, allowing unauthenticated stored XSS via the Card Type parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Gravity Forms to version 2.9.31 or later which contains the fix for proper input sanitization and output escaping. If immediate update is not possible, restrict access to form entry dashboards or disable the plugin.

Recommended fix Moderate confidence

2.9.31 or later

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard > Plugins section.
  3. 3. Locate Gravity Forms plugin and check for available updates.
  4. 4. Update Gravity Forms to version 2.9.31 or later.
  5. 5. Verify the update was successful by checking the plugin version number.
  6. 6. Test that form entries can still be viewed in the admin dashboard without errors.
  7. 7. Confirm the stored XSS vulnerability is remediated by attempting to submit a form with malicious script in the Card Type field (input_<id>.4) - the script should now be properly escaped.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4394 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data