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

> Remote attackers can execute arbitrary code via shell metacharacters in the Ploticus module of PhpWiki.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 11 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-568c-r828-v9mv

## What is CVE-2014-5519?

CVE-2014-5519 is a high-severity command injection vulnerability in n/a, published on 11 Sep 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Ploticus module in PhpWiki 1.5.0 allows remote attackers to execute arbitrary code via shell metacharacters in a device option in the edit[content] parameter to index.php/HeIp.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Phpwiki Project Phpwiki.

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

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

## Is CVE-2014-5519 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5519 exists.

Public exploit code:

- PhpWiki - Remote Command Execution (exploitdb)
- Phpwiki Ploticus Remote Code Execution (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5519 is a high-severity command injection vulnerability in n/a, published on 11 Sep 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5519 exists.

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-5519/ (Markdown: https://insights.sbomify.com/CVE-2014-5519/index.md)
```

## Sources

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

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