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

> Authenticated attackers can upload malicious files to execute arbitrary code on Dotclear blog servers.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 18 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r592-jw3g-mc38

## What is CVE-2008-3232?

CVE-2008-3232 is a critical vulnerability in n/a, published on 18 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in ecrire/images.php in Dotclear 1.2.7.1 and earlier allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in images.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Dotclear Dotclear.

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

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

## Is CVE-2008-3232 being exploited?

There is no known exploitation of CVE-2008-3232 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-3957](https://insights.sbomify.com/CVE-2005-3957/): Other in n/a (critical 10.0)
- [CVE-2015-8832](https://insights.sbomify.com/CVE-2015-8832/): File upload in n/a (high 8.8)
- [CVE-2016-7902](https://insights.sbomify.com/CVE-2016-7902/): File upload in n/a (high 8.8)
- [CVE-2023-53952](https://insights.sbomify.com/CVE-2023-53952/): Dotclear 2.25.3 Authenticated Remote Code Execution via File Upload (high 8.7)
- [CVE-2024-58281](https://insights.sbomify.com/CVE-2024-58281/): Dotclear 2.29 Remote Code Execution via Authenticated File Upload (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3232 is a critical vulnerability in n/a, published on 18 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3232 in the wild and no public exploit code.

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-3232/ (Markdown: https://insights.sbomify.com/CVE-2008-3232/index.md)
```

## Sources

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

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