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

> Remote attackers can bypass upload filters to execute arbitrary code via double extensions if script execution is enabled in the pub directory.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/I:P/A:N`)
- **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:** 5 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jm78-jvf9-4c96

## What is CVE-2006-3336?

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

### Official description

TWiki 01-Dec-2000 up to 4.0.3 allows remote attackers to bypass the upload filter and execute arbitrary code via filenames with double extensions such as ".php.en", ".php.1", and other allowed extensions that are not .txt.  NOTE: this is only a vulnerability when the server allows script execution in the pub directory.

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

It affects 1 product.


Products: Twiki Twiki.

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

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

## Is CVE-2006-3336 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5305](https://insights.sbomify.com/CVE-2008-5305/): Code injection in n/a (critical 10.0)
- [CVE-2013-1751](https://insights.sbomify.com/CVE-2013-1751/): Command injection in n/a (critical 9.8)
- [CVE-2005-3056](https://insights.sbomify.com/CVE-2005-3056/): Command injection in n/a (critical 9.8)
- [CVE-2014-7236](https://insights.sbomify.com/CVE-2014-7236/): Code injection in n/a (critical 9.1)
- [CVE-2006-6071](https://insights.sbomify.com/CVE-2006-6071/): Auth bypass in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3336 is a medium-severity vulnerability in n/a, published on 5 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3336 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-2006-3336/ (Markdown: https://insights.sbomify.com/CVE-2006-3336/index.md)
```

## Sources

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

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