Content Audit <= 1.6.0 - Authenticated (Admin+) SQL Injection
Strategic Overview
- Status
- Patched in 1.6.1
- Affected Plugin
- Content Audit
- Affected Version
< 1.6.1- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2014-5389
At a glance
CVE-2014-5389 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Content Audit WordPress plugin, affecting versions < 1.6.1. 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 at Admin level or above. The issue is fixed in version 1.6.1; sites on affected versions should update now. Disclosed October 2014, reported by Mallory Adams.
Vulnerability Overview
SQL injection vulnerability in content-audit-schedule.php in the Content Audit plugin before 1.6.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the "Audited content types" option in the content-audit page to wp-admin/options-general.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 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 Content Audit < 1.6.1 takes an account at Admin level or above. 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 Content Audit the fix is 1.6.1: builds < 1.6.1 are affected, anything from 1.6.1 onward is not.
Remediation
Update to version 1.6.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Content Audit 1.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Content Audit
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C