CVE-2026-5113: Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Consent Field Hidden Input
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Consent field hidden inputs in versions up to and including 2.10.0. This is due to a flawed state validation mechanism that fails open when input is sanitized by wpkses(), combined with insufficient output escaping. The state validation logic creates two hashes (raw input and wpkses-sanitized input) and only fails validation if BOTH hashes don't match the original state. When an attacker injects XSS payloads using tags stripped by wpkses() (like <svg>), the sanitized hash matches while the malicious raw value is preserved and saved to the database. When administrators view the Entries List page, the stored malicious consent label is retrieved and output without escaping, causing the XSS payload to execute. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in entries that will execute whenever an authenticated administrator accesses the entries list page.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5113?
CVE-2026-5113 has a medium severity rating due to its potential for resulting in stored Cross-Site Scripting attacks.
How do I fix CVE-2026-5113?
To fix CVE-2026-5113, update the Gravity Forms plugin to version 2.10.1 or later where the vulnerability has been addressed.
Who is affected by CVE-2026-5113?
CVE-2026-5113 affects users of Gravity Forms versions up to and including 2.10.0.
What type of vulnerability is CVE-2026-5113?
CVE-2026-5113 is categorized as an Unauthenticated Stored Cross-Site Scripting vulnerability.
Can CVE-2026-5113 be exploited without authentication?
Yes, CVE-2026-5113 can be exploited without authentication, making it more dangerous for users.