# CVE-2005-4132: Code injection in n/a

> Remote attackers can execute arbitrary code via remote file inclusion in Contenido CMS when specific PHP settings are enabled.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 9 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hjg4-m8gp-mxjw

## What is CVE-2005-4132?

CVE-2005-4132 is a high-severity code injection vulnerability in n/a, published on 9 Dec 2005. It can be exploited over the network.

### Official description

Unspecified "security leak" vulnerability in Contenido before 4.6.4, when register_globals is on and allow_url_fopen is true, has unspecified impact and attack vectors.  NOTE: it is likely that this is a PHP remote file include vulnerability.

## Which versions are affected by CVE-2005-4132?

It affects 1 product.


Products: Contenido Contendio.

## How do I fix CVE-2005-4132?

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

## Is CVE-2005-4132 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5380](https://insights.sbomify.com/CVE-2006-5380/): File upload 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-2005-4132 and fix it if it is affected.

What it is: CVE-2005-4132 is a high-severity code injection vulnerability in n/a, published on 9 Dec 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-4132 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-2005-4132/ (Markdown: https://insights.sbomify.com/CVE-2005-4132/index.md)
```

## Sources

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

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