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

> Remote attackers can execute arbitrary code by uploading malicious files with executable extensions disguised as images in OneCMS.

- **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:** 11 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-68j2-2v53-vhg2

## What is CVE-2008-7209?

CVE-2008-7209 is a high-severity vulnerability in n/a, published on 11 Sep 2009. It can be exploited over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the add2 action in a_upload.php in OneCMS 2.4, and possibly earlier, allows remote attackers to execute arbitrary code by uploading a file with an executable extension and using a safe content type such as image/gif, then accessing it via a direct request to the file in an unspecified directory.

Weakness: CWE-264

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

It affects 1 product.


Products: Insane Visions Onecms.

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

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

## Is CVE-2008-7209 being exploited?

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

Public exploit code:

- OneCMS 2.4 - SQL Injection / Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5016](https://insights.sbomify.com/CVE-2007-5016/): SQL injection in n/a (high 7.5)
- [CVE-2008-7208](https://insights.sbomify.com/CVE-2008-7208/): SQL injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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