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

> Remote attackers can upload and execute arbitrary PHP code via unrestricted file upload in FCKeditor when Apache mod_mime is enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/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:** 6 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-92qr-f662-7vcr

## What is CVE-2006-3362?

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

### Official description

Unrestricted file upload vulnerability in connectors/php/connector.php in FCKeditor mcpuk file manager, as used in (1) Geeklog 1.4.0 through 1.4.0sr3, (2) toendaCMS 1.0.0 Shizouka Stable and earlier, (3) WeBid 0.5.4, and possibly other products, when installed on Apache with mod_mime, allows remote attackers to upload and execute arbitrary PHP code via a filename with a .php extension and a trailing extension that is allowed, such as .zip.

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

It affects 2 products.


Products: Geeklog Geeklog, Toenda Software Development Toendacms.

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

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

## Is CVE-2006-3362 being exploited?

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

Public exploit code:

- GeekLog 1.4.0sr3 - 'f(u)ckeditor' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1069](https://insights.sbomify.com/CVE-2006-1069/): Privilege escalation in n/a (critical 10.0)
- [CVE-2006-2698](https://insights.sbomify.com/CVE-2006-2698/): Information disclosure in n/a (high 7.8)
- [CVE-2010-4933](https://insights.sbomify.com/CVE-2010-4933/): SQL injection in n/a (high 7.5)
- [CVE-2007-2793](https://insights.sbomify.com/CVE-2007-2793/): Code injection in n/a (high 7.5)
- [CVE-2007-0810](https://insights.sbomify.com/CVE-2007-0810/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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