Strategic Overview
- Status
- Patched in 1.0.34
- Affected Plugin
- Mingle Forum
- Affected Version
<= 1.0.33.3- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2013-0735
At a glance
CVE-2013-0735 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Mingle Forum WordPress plugin, affecting versions <= 1.0.33.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.34; sites on affected versions should update now. Disclosed February 2013, reported by Charlie Eriksen.
Vulnerability Overview
Multiple SQL injection vulnerabilities in wpf.class.php in the Mingle Forum plugin before 1.0.34 for WordPress allow remote attackers to execute arbitrary SQL commands via the id parameter in a viewtopic (1) remove_post, (2) sticky, or (3) closed action or (4) thread parameter in a postreply action to index.php.
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. 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 Mingle Forum <= 1.0.33.3 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 Mingle Forum the fix is 1.0.34: builds <= 1.0.33.3 are affected, anything from 1.0.34 onward is not.
Remediation
Update to version 1.0.34, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Mingle Forum: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Mingle Forum 1.0.34 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C