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

> Authenticated administrators can execute arbitrary SQL commands via the story parameter in the stripShow plugin for WordPress.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-293h-cqj2-8x83

## What is CVE-2014-5184?

CVE-2014-5184 is a medium-severity SQL injection vulnerability in n/a, published on 6 Aug 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in the stripshow-storylines page in the stripShow plugin 2.5.2 for WordPress allows remote authenticated administrators to execute arbitrary SQL commands via the story parameter in an edit action to wp-admin/admin.php.

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

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

It affects 1 product.


Products: Stripshow Plugin Project Stripshow.

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

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

## Is CVE-2014-5184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5184 is a medium-severity SQL injection vulnerability in n/a, published on 6 Aug 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-5184 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-5184/ (Markdown: https://insights.sbomify.com/CVE-2014-5184/index.md)
```

## Sources

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

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