WDContactFormBuilder <= 1.0.24 - Authenticated Blind SQL Injection
Strategic Overview
- Status
- Patched in 1.0.25
- Affected Plugin
- WDContactFormBuilder
- Affected Version
<= 1.0.24- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WDContactFormBuilder WordPress plugin, affecting versions <= 1.0.24. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.0.25; sites on affected versions should update now. Disclosed July 2015, reported by Marcin Probola.
Vulnerability Overview
The Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via the 'order_by' parameter in versions up to, and including, 1.0.24 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 Admin+ 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')
WDContactFormBuilder <= 1.0.24 carries this weakness at order_by, and reaching it takes any authenticated account. 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 WDContactFormBuilder the fix is 1.0.25: builds <= 1.0.24 are affected, anything from 1.0.25 onward is not.
Remediation
Update to version 1.0.25, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WDContactFormBuilder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WDContactFormBuilder 1.0.25 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WDContactFormBuilder
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C