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.
References6
- docs.gravityforms.com/gravityforms-change-log/
- plugins.trac.wordpress.org/browser/gravityforms/tags/2.9.25/inc…
- plugins.trac.wordpress.org/browser/gravityforms/tags/2.9.25/inc…
- plugins.trac.wordpress.org/browser/gravityforms/trunk/includes/…
- plugins.trac.wordpress.org/browser/gravityforms/trunk/includes/…
- www.wordfence.com/threat-intel/vulnerabilities/id/6f38d7b7-6df6…
Metrics
- CVSS 3.1
-
6.1
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 23 · as of 12 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.