Gravityforms <= 1.9.6 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.9.7
- Affected Plugin
- Gravity Forms
- Affected Version
<= 1.9.6- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Gravity Forms WordPress plugin, affecting versions <= 1.9.6. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.9.7; sites on affected versions should update now. Disclosed April 2015, reported by DANIEL CID.
Vulnerability Overview
The Gravityforms plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 1.9.6 due to insufficient input sanitization and output escaping alongside the use of add_query_arg or remove_query_arg(). This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Gravity Forms <= 1.9.6 carries this weakness at remove_query_arg(), and reaching it takes a caller who can reach the endpoint. 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 1.9.7: builds <= 1.9.6 are affected, anything from 1.9.7 onward is not.
Remediation
Update to version 1.9.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Gravity Forms: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gravity Forms 1.9.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 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 - 7.2CVE-2026-5109: Gravity Forms <= 2.10.0 Stored Cross-Site Scripting
CVE-2026-5109
Other vulnerabilities in Gravity Forms
- 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 - 8.1CVE-2026-19513: Gravity Forms <= 3.0.2 Arbitrary File Upload
CVE-2026-19513 - 8.1CVE-2025-12974: Gravity Forms <= 2.9.21.1 Arbitrary File Upload
CVE-2025-12974
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C