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

> Remote attackers can execute arbitrary PHP code via remote file inclusion in Contenido CMS, requiring immediate patching.

- **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:** 18 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-42q3-f5fp-gpxr

## What is CVE-2006-5380?

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

### Official description

Remote file inclusion vulnerability in Contenido CMS allows remote attackers to execute arbitrary PHP code via a URL in the contenido_path parameter to (1) cms/dbfs.php or (2) cms/front_content.php.  NOTE: CVE disputes this issue for version 4.6.15, because $contenido_path is set to a static value

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

It affects 1 product.


Products: Contenido Contendio.

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

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

## Is CVE-2006-5380 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4132](https://insights.sbomify.com/CVE-2005-4132/): Code injection in n/a (high 7.5)
- [CVE-2006-5381](https://insights.sbomify.com/CVE-2006-5381/): Information disclosure in n/a (medium 5.0)
- [CVE-2008-2911](https://insights.sbomify.com/CVE-2008-2911/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2014-9433](https://insights.sbomify.com/CVE-2014-9433/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5380 is a high-severity vulnerability in n/a, published on 18 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5380 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-5380/ (Markdown: https://insights.sbomify.com/CVE-2006-5380/index.md)
```

## Sources

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

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