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

> Remote attackers could execute arbitrary PHP code via remote file inclusion in the lmtg_myhomepage component for Mambo, though the vulnerability is disputed.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2006
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-r2ph-84cc-pg9v

## What is CVE-2006-4264?

CVE-2006-4264 is a critical code injection vulnerability in n/a, published on 21 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in the lmtg_myhomepage Component (com_lmtg_myhomepage) for Mambo allow remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter in (1) install.lmtg_homepage.php and (2) mtg_homepage.php.  NOTE: this issue has been disputed by a third party, who states that the $mosConfig_absolute_path variable is only used within a function definition.  CVE source code analysis on 20060824 is not conclusive but tends to concur with the dispute.  In addition, it appears that the component name is actually "lmtg_myhomepage"

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

It affects 1 product.


Products: Mambo Mtg Myhomepage Component.

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

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

## Is CVE-2006-4264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4264 is a critical code injection vulnerability in n/a, published on 21 Aug 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-4264 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-4264/ (Markdown: https://insights.sbomify.com/CVE-2006-4264/index.md)
```

## Sources

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

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