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

> Authenticated users can upload executable files as logos to achieve remote code execution on the server.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 11 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-38p7-f895-f9ch

## What is CVE-2008-6928?

CVE-2008-6928 is a medium-severity vulnerability in n/a, published on 11 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in PHPStore Complete Classifieds allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension as a logo, then accessing it via a direct request to the file in classifieds1/yellow_images/.

Weakness: CWE-264

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

It affects 1 product.


Products: Phpstore Complete Classifieds.

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

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

## Is CVE-2008-6928 being exploited?

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

Public exploit code:

- PHPStore Complete Classifieds Script - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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