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

> Remote attackers can upload PHP code via unrestricted file upload in the Contact component, leading to arbitrary code execution.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-crg7-c4x5-jq8x

## What is CVE-2006-4859?

CVE-2006-4859 is a high-severity vulnerability in n/a, published on 19 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in contact.html.php in the Contact (com_contact) component in Limbo (aka Lite Mambo) CMS 1.0.4.2L and earlier allows remote attackers to upload PHP code to the images/contact folder via a filename with a double extension in the contact_attach parameter in a contact option in index.php, which bypasses an insufficiently restrictive regular expression.

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

It affects 1 product.


Products: Limbo Cms Limbo Cms.

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

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

## Is CVE-2006-4859 being exploited?

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

Public exploit code:

- Limbo CMS 1.0.4.2L - 'com_contact' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4860](https://insights.sbomify.com/CVE-2006-4860/): Other in n/a (critical 10.0)
- [CVE-2008-0734](https://insights.sbomify.com/CVE-2008-0734/): SQL injection in n/a (high 7.5)
- [CVE-2006-1662](https://insights.sbomify.com/CVE-2006-1662/): Code injection in n/a (high 7.5)
- [CVE-2005-4317](https://insights.sbomify.com/CVE-2005-4317/): Code injection in n/a (medium 6.8)
- [CVE-2006-2142](https://insights.sbomify.com/CVE-2006-2142/): Code injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4859 is a high-severity vulnerability in n/a, published on 19 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4859 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-4859/ (Markdown: https://insights.sbomify.com/CVE-2006-4859/index.md)
```

## Sources

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

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