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

> Authenticated editors can execute arbitrary SQL commands via the targetmenu parameter in the Simple Retail Menus plugin.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-573v-6g2j-5865

## What is CVE-2014-5183?

CVE-2014-5183 is a medium-severity SQL injection vulnerability in n/a, published on 6 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in includes/mode-edit.php in the Simple Retail Menus (simple-retail-menus) plugin before 4.1 for WordPress allows remote authenticated editors to execute arbitrary SQL commands via the targetmenu 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-5183?

It affects 1 product.


Products: Simple Retail Menus Plugin Project Simple-Retail-Menus.

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

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

## Is CVE-2014-5183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5183 is a medium-severity SQL injection vulnerability in n/a, published on 6 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-5183 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-5183/ (Markdown: https://insights.sbomify.com/CVE-2014-5183/index.md)
```

## Sources

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

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