# CVE-2014-5014: Command injection in n/a

> Remote attackers can execute arbitrary commands via invalid characters in the image_magic_path parameter of the WordPress Flash Uploader plugin.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p2gr-mqhh-c93j

## What is CVE-2014-5014?

CVE-2014-5014 is a critical command injection vulnerability in n/a, published on 25 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WordPress Flash Uploader plugin before 3.1.3 for WordPress allows remote attackers to execute arbitrary commands via vectors related to invalid characters in image_magic_path.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Tinywebgallery Wordpress Flash Uploader.

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

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

## Is CVE-2014-5014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5014 is a critical command injection vulnerability in n/a, published on 25 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-5014 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-5014/ (Markdown: https://insights.sbomify.com/CVE-2014-5014/index.md)
```

## Sources

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

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