# CVE-2006-5045: Code injection in n/a

> Remote attackers can execute arbitrary code via PHP remote file inclusion in the PollXT component for Joomla!.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 27 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6g7v-43xg-47vc

## What is CVE-2006-5045?

CVE-2006-5045 is a medium-severity code injection vulnerability in n/a, published on 27 Sep 2006. It can be exploited over the network.

### Official description

Unspecified vulnerability in PollXT component (com_pollxt) 1.22.07 and earlier for Joomla! has unspecified impact and attack vectors, probably related to PHP remote file inclusion in the mosConfig_absolute_path to conf.pollxt.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Joomlaxt Com Pollxt.

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

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

## Is CVE-2006-5045 being exploited?

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

Public exploit code:

- Mambo Component pollxt 1.22.07 - Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5045 is a medium-severity code injection vulnerability in n/a, published on 27 Sep 2006. It can be exploited over the network.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5045 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-5045/ (Markdown: https://insights.sbomify.com/CVE-2006-5045/index.md)
```

## Sources

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

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