CVE-2026-4394 Gravity Forms <= 2.9.30 - Unauthenticated Stored Cross-Site Scripting via Credit Card 'Card Type' Sub-Field

Q: What is CVE-2026-4394?

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.

Medium 6.1 Published 7 Apr 2026 Updated 8 Apr 2026

Unauthenticated attackers can inject scripts via the Credit Card field, leading to code execution when administrators view entries.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: None listed

What is CVE-2026-4394?

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.

Official 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_<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.

Weakness: CWE-79

Which versions are affected by CVE-2026-4394?

How do I fix CVE-2026-4394?

No fix has been published for CVE-2026-4394 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-4394 being exploited?

There is no known exploitation of CVE-2026-4394 in the wild and no public exploit code.

Sources

Also known as GHSA-5pv5-mj98-fr8x.