# CVE-2014-1216: Improper Neutralization of Special Elements used in a Command in FitNesse Wiki

> Remote attackers can execute arbitrary commands by manipulating page content parameters in FitNesse Wiki, requiring low privileges.

- **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:** Yes
- **Published:** 21 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mpx3-mx2p-9gv3

## What is CVE-2014-1216?

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

### Official description

FitNesse Wiki 20131110, 20140201, and earlier allows remote attackers to execute arbitrary commands by defining a COMMAND_PATTERN and TEST_RUNNER in the pageContent parameter when editing a page.

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

2 open source packages ship an affected version, including org.fitnesse:fitnesse. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.fitnesse:fitnesse` | Maven | From 20131110 | 20140418 |
| `org.fitnesse:fitnesse` | Maven | From 20131110 | 20140418 |

Products: Fitnesse Fitnesse Wiki.

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

Upgrade org.fitnesse:fitnesse to 20140418 or later.

## Is CVE-2014-1216 being exploited?

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

Public exploit code:

- Fitnesse Wiki - Remote Command Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1216 is a high-severity command injection vulnerability in n/a, published on 21 Apr 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-1216 exists.

Affected packages and fixed versions:
- org.fitnesse:fitnesse (Maven): affected from 20131110; fixed in 20140418
- org.fitnesse:fitnesse (Maven): affected from 20131110; fixed in 20140418

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

## Sources

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

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