# CVE-2024-28125: FitNesse allows execution of arbitrary OS commands

> Remote authenticated attackers can execute arbitrary OS commands in FitNesse, though the vendor disputes this as intended behavior.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 18 Mar 2024
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-x9r9-48rm-4xm6

## What is CVE-2024-28125?

CVE-2024-28125 is a critical command injection vulnerability in unclebob FitNesse, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FitNesse all releases allows a remote authenticated attacker to execute arbitrary OS commands. Note: A contributor of FitNesse has claimed that this is not a vulnerability but a product specification and this is currently under further investigation.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-28125?

2 open source packages ship an affected version, including org.fitnesse:fitnesse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.fitnesse:fitnesse` | Maven | All versions to 20240707 | None |
| `org.fitnesse:fitnesse` | Maven | All versions to 20240707 | None |

## How do I fix CVE-2024-28125?

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

## Is CVE-2024-28125 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28125 and fix it if it is affected.

What it is: CVE-2024-28125 is a critical command injection vulnerability in unclebob FitNesse, published on 18 Mar 2024. 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-2024-28125 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.fitnesse:fitnesse (Maven): affected all versions up to 20240707; no fix listed
- org.fitnesse:fitnesse (Maven): affected all versions up to 20240707; no fix listed

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

## Sources

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

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