# CVE-2009-20006: osCommerce <= 2.2 Admin File Manager Arbitrary PHP Code Execution

> Unauthenticated attackers can upload and execute arbitrary PHP files via the admin file manager, leading to remote code execution on the server.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-2h4r-77vh-7qcf

## What is CVE-2009-20006?

CVE-2009-20006 is a critical vulnerability in osCommerce, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

osCommerce versions up to and including 2.2 RC2a contain a vulnerability in its administrative file manager utility (admin/file_manager.php). The interface allows file uploads and edits without sufficient input validation or access control. An unauthenticated attacker can craft a POST request to upload a .php file containing arbitrary code, which is then executed by the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2009-20006 being exploited?

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

Public exploit code:

- osCommerce 2.2 Arbitrary PHP Code Execution (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-20006 is a critical vulnerability in osCommerce, published on 16 Sep 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-20006 exists.

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

## Sources

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

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