# CVE-2008-6822: File upload in n/a

> Remote attackers can execute arbitrary code by uploading malicious files with executable extensions to the image uploader.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5crv-v5hr-vpjw

## What is CVE-2008-6822?

CVE-2008-6822 is a high-severity vulnerability in n/a, published on 4 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in uploadp.php in New Earth Programming Team (NEPT) imgupload (aka Image Uploader) 1.0 allows remote attackers to execute arbitrary code by uploading a file with an executable extension and a modified content type, then accessing this file via a direct request, as demonstrated by an upload with an image/jpeg content type.  NOTE: some of these details are obtained from third party information.

## Which versions are affected by CVE-2008-6822?

It affects 1 product.


Products: Newearthpt Imgupload.

## How do I fix CVE-2008-6822?

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

## Is CVE-2008-6822 being exploited?

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

Public exploit code:

- NEPT Image Uploader 1.0 - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6822 and fix it if it is affected.

What it is: CVE-2008-6822 is a high-severity vulnerability in n/a, published on 4 Jun 2009. 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-2008-6822 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-2008-6822/ (Markdown: https://insights.sbomify.com/CVE-2008-6822/index.md)
```

## Sources

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

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