CVE-2026-5112 Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Calculation Product Field in Repeater
Unauthenticated attackers can inject scripts via Gravity Forms calculation fields, executing code in admin browsers to potentially take over accounts.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-5112?
CVE-2026-5112 is a high-severity cross-site scripting vulnerability in Gravity Forms, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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 of Calculation Product field product names when rendered inside Repeater fields. The validate() method in the GF_Field_Calculation class only validates the quantity field (.3) and completely ignores the product name field (.1), allowing malicious HTML to pass through validation. When the value is saved, the sanitize_entry_value() method returns the raw value without sanitization for fields where HTML is not expected. Subsequently, when an entry is viewed in wp-admin, the get_value_entry_detail() method concatenates the unescaped product name directly into the output string, which is then rendered by the repeater's get_value_entry_detail() method without further escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via form submissions that will execute whenever an authenticated administrator with the gravityforms_view_entries capability accesses the entry detail page.
Weakness: CWE-79
Which versions are affected by CVE-2026-5112?
How do I fix CVE-2026-5112?
No fix has been published for CVE-2026-5112 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-5112 being exploited?
There is no known exploitation of CVE-2026-5112 in the wild and no public exploit code.
Sources
Also known as GHSA-2qgr-m7c7-j745.