CVE-2026-5110: Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Single Product Field Inside Repeater
The Gravity Forms plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping in the SingleProduct field when used inside a Repeater field. When SingleProduct fields are nested within Repeater fields, the validation flow bypasses the state validation mechanism (failedstatevalidation()) that would normally prevent tampering with field values. The validatesubfield() method only calls the field's validate() method, which for SingleProduct fields only validates the quantity field and does not check the product name field for tampering. As a result, an attacker can inject arbitrary HTML and JavaScript into the product name field (input .1). This malicious input is then saved to the database without sanitization because sanitizeentryvalue() returns raw values when HTML is not expected for the field type. When an administrator views the entry in wp-admin/admin.php?page=gfentries, the getvalueentrydetail() method outputs the product name without escaping, causing the stored XSS payload to execute in the administrator's browser. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses an entry containing the malicious payload.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5110?
The severity of CVE-2026-5110 is considered high due to the possibility of unauthenticated stored cross-site scripting.
How do I fix CVE-2026-5110?
To fix CVE-2026-5110, update the Gravity Forms plugin to version 2.10.1 or later.
What versions are affected by CVE-2026-5110?
CVE-2026-5110 affects all versions of Gravity Forms up to and including 2.10.0.
What type of vulnerability is CVE-2026-5110?
CVE-2026-5110 is an unauthenticated stored cross-site scripting vulnerability.
Can CVE-2026-5110 be exploited without authentication?
Yes, CVE-2026-5110 can be exploited without authentication, making it particularly dangerous.