Strategic Overview
- Status
- Patched in 1.9.3.6
- Affected Plugin
- Gravity Forms
- Affected Version
<= 1.9.3.5- CVSS
- 9.1Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2015-2260
At a glance
CVE-2015-2260 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Gravity Forms WordPress plugin, affecting versions <= 1.9.3.5. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.9.3.6; sites on affected versions should update now. Disclosed March 2015, reported by Scott Kingsley Clark.
Vulnerability Overview
The Gravifyforms plugin for WordPress is vulnerable to blind SQL Injection via the ‘sort_column GET’ parameter in versions up to, and including,1.9.3.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Gravity Forms <= 1.9.3.5 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Gravity Forms the fix is 1.9.3.6: builds <= 1.9.3.5 are affected, anything from 1.9.3.6 onward is not.
Remediation
Update to version 1.9.3.6, 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.3.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
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 - 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 - 7.5CVE-2026-12997: Gravity Forms <= 2.10.4 Arbitrary File Read
CVE-2026-12997
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C