CVE-2014-5389
Content Audit Project Content Audit vulnerability
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.
Affected products
Content Audit. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Content Audit Project Content Audit runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- packetstormsecurity.com/files/128525/WordPress-Content-Audit-1.6-Blind-SQL-Injection.html · Exploit
- seclists.org/fulldisclosure/2014/Oct/8 · Exploit
- security.dxw.com/advisories/blind-sqli-vulnerability-in-content-audit-could-allow-a-privil · Exploit
- www.securityfocus.com/bid/70214
- wordpress.org/plugins/content-audit/changelog
- nvd.nist.gov/vuln/detail/CVE-2014-5389
- cve.org/CVERecord?id=CVE-2014-5389
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.