# CVE-2006-3381: File upload in n/a

> Remote attackers can execute arbitrary PHP code by uploading and accessing a malicious file, though this may be intended functionality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6pjg-r8w7-49w9

## What is CVE-2006-3381?

CVE-2006-3381 is a high-severity vulnerability in n/a, published on 6 Jul 2006. It can be exploited over the network, with no action from the victim.

### Official description

SturGeoN Upload allows remote attackers to execute arbitrary PHP code by uploading a file with a .php extension, then directly accessing the file.  NOTE: It is uncertain whether this is a vulnerability or a feature of the product.

## Which versions are affected by CVE-2006-3381?

It affects 1 product.


Products: Sturgeon Upload Sturgeon Upload.

## How do I fix CVE-2006-3381?

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

## Is CVE-2006-3381 being exploited?

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

Public exploit code:

- SturGeoN Upload - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3381 and fix it if it is affected.

What it is: CVE-2006-3381 is a high-severity vulnerability in n/a, published on 6 Jul 2006. It can be exploited 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-2006-3381 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-2006-3381/ (Markdown: https://insights.sbomify.com/CVE-2006-3381/index.md)
```

## Sources

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

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