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

> Remote attackers can upload and execute arbitrary PHP files by embedding code in image files, leading to code execution on the server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c3h7-7xr3-rp4r

## What is CVE-2006-6338?

CVE-2006-6338 is a medium-severity vulnerability in n/a, published on 7 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in upload/index.php in deV!L`z Clanportal (DZCP) before 1.3.6.1 allows remote attackers to upload and execute arbitrary .php files by embedding PHP code in a JPEG or GIF file that is uploaded to inc/images/uploads/userpics/.

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

It affects 1 product.


Products: Devilz Clanportal Devilz Clanportal.

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

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

## Is CVE-2006-6338 being exploited?

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

Public exploit code:

- DZCP (deV!L_z Clanportal) 1.3.6 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-3347](https://insights.sbomify.com/CVE-2006-3347/): SQL injection in n/a (high 7.5)
- [CVE-2006-6339](https://insights.sbomify.com/CVE-2006-6339/): SQL injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6338 is a medium-severity vulnerability in n/a, published on 7 Dec 2006. 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-2006-6338 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-6338/ (Markdown: https://insights.sbomify.com/CVE-2006-6338/index.md)
```

## Sources

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

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