CVE-2026-4394 MEDIUM

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

Vendor Gravity Forms
Product Gravity Forms
Weakness CWE-79 · XSS
Published April 7, 2026
Last update April 8, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Gravity Forms versions 2.9.30 and earlier contain a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. The vulnerability requires user interaction—typically clicking a malicious link—and can affect users across different parts of the site. An attacker with no authentication can craft a payload that executes in a victim's browser.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in other users' browsers when they visit a crafted link.

Potential impact on your site

04Site Impact

Site visitors can be redirected, have sessions hijacked, or have their data stolen if they click a malicious link.

Conditions required to exploit

05Prerequisites

Victim must click a malicious link or visit an attacker-controlled page; no authentication required.

Key dates

06Disclosure timeline

April 7, 2026 CVE published
April 8, 2026 Record updated