Gravity Forms <= 3.1.1 - Unauthenticated Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values
Strategic Overview
- Status
- Patched in 3.1.2
- Affected Plugin
- Gravity Forms
- Affected Version
<= 3.1.1- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation
- CVE
CVE-2026-90437
At a glance
CVE-2026-90437 is a high-severity Improper Neutralization of Input During Web Page Generation vulnerability in the Gravity Forms WordPress plugin, affecting versions <= 3.1.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.2; sites on affected versions should update now. Disclosed October 2026, reported by daroo.
Vulnerability Overview
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values in all versions up to, and including, 3.1.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because Post Excerpt, Post Custom Field, and Rich-Text-Editor-enabled Paragraph Text fields allow raw HTML submissions via allow_html(), and an entity-encoded payload stored in a data-dialog-confirm attribute evades wp_kses_post() at save time but is decoded into executable markup by the browser when the plugin's admin JavaScript passes the attribute value to insertAdjacentHTML().
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation
Gravity Forms <= 3.1.1 carries this weakness at allow_html(), and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Gravity Forms the fix is 3.1.2: builds <= 3.1.1 are affected, anything from 3.1.2 onward is not.
Remediation
Update to version 3.1.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gravity Forms 3.1.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-97645: Gravity Forms <= 3.1.2 Stored Cross-Site Scripting
CVE-2026-97645 - 7.2CVE-2026-16649: Gravity Forms <= 2.10.5 Stored Cross-Site Scripting
CVE-2026-16649 - 7.2CVE-2026-5113: Gravity Forms <= 2.9.30 Stored Cross-Site Scripting
CVE-2026-5113 - 7.2CVE-2026-5112: Gravity Forms <= 2.10.0 Stored Cross-Site Scripting
CVE-2026-5112
Other vulnerabilities in Gravity Forms
- 9.8CVE-2026-103039: Gravity Forms <= 3.1.2 PHP Object Injection
CVE-2026-103039 - 9.8CVE-2026-84434: Gravity Forms <= 3.1.0.4 Arbitrary File Upload
CVE-2026-84434 - 9.8CVE-2025-13407: Gravity Forms <= 2.9.23.0 Arbitrary File Upload
CVE-2025-13407 - 9.8CVE-2025-12352: Gravity Forms <= 2.9.20 Arbitrary File Upload
CVE-2025-12352 - 9.8CVE-2023-28782: Gravity Forms <= 2.7.3 PHP Object Injection
CVE-2023-28782 - 9.8Gravityforms <= 1.8.19 Arbitrary File Upload
- 9.1CVE-2026-48866: Gravity Forms <= 2.10.0.1 Arbitrary File Deletion
CVE-2026-48866 - 9.1CVE-2015-2260: Gravityforms <= 1.9.3.5 SQL Injection
CVE-2015-2260
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C