# CVE-2009-20011: ContentKeeper Web Appliance < 125.10 RCE via mimencode

> Unauthenticated attackers can execute arbitrary commands and potentially gain root access via insecure file uploads and PATH abuse in ContentKeeper Web Appliances.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-w8w9-prcc-w4vw

## What is CVE-2009-20011?

CVE-2009-20011 is a critical command injection vulnerability in ContentKeeper Web Appliance, published on 30 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ContentKeeper Web Appliance (now maintained by Impero Software) versions prior to 125.10 are vulnerable to remote command execution due to insecure handling of file uploads via the mimencode CGI utility. The vulnerability allows unauthenticated attackers to upload and execute arbitrary scripts as the Apache user. Additionally, the exploit can optionally escalate privileges by abusing insecure PATH usage in the benetool binary, resulting in root-level access if successful.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2009-20011?


## How do I fix CVE-2009-20011?

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

## Is CVE-2009-20011 being exploited?

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

Public exploit code:

- ContentKeeper Web Remote Command Execution (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-20011 and fix it if it is affected.

What it is: CVE-2009-20011 is a critical command injection vulnerability in ContentKeeper Web Appliance, published on 30 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-20011 exists.

Affected product: ContentKeeper Web Appliance. 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-2009-20011/ (Markdown: https://insights.sbomify.com/CVE-2009-20011/index.md)
```

## Sources

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

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