# CVE-2014-5389: SQL injection in n/a

> Remote attackers with admin privileges can execute arbitrary SQL commands via the Content Audit plugin's settings page.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r8gp-f9pj-hx94

## What is CVE-2014-5389?

CVE-2014-5389 is a high-severity SQL injection vulnerability in n/a, published on 6 Oct 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2014-5389?

It affects 1 product.


Products: Content Audit Project Content Audit.

## How do I fix CVE-2014-5389?

No fix has been published for CVE-2014-5389 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-5389 being exploited?

There is no known exploitation of CVE-2014-5389 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-18560](https://insights.sbomify.com/CVE-2017-18560/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5389 and fix it if it is affected.

What it is: CVE-2014-5389 is a high-severity SQL injection vulnerability in n/a, published on 6 Oct 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-5389 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-5389/ (Markdown: https://insights.sbomify.com/CVE-2014-5389/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-5389
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-5389
- OSV: https://osv.dev/vulnerability/CVE-2014-5389

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-5389/
Summaries are generated and may contain mistakes; the official description above is the record.