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

> Remote attackers can execute arbitrary PHP code in Nucleus CMS via remote file inclusion in multiple scripts.

- **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:** 22 Jun 2006
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-76h5-j8hw-99ch

## What is CVE-2006-3136?

CVE-2006-3136 is a critical code injection vulnerability in n/a, published on 22 Jun 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 Nucleus 3.23 allow remote attackers to execute arbitrary PHP code via a URL the DIR_LIBS parameter in (1) path/action.php, and to files in path/nucleus including (2) media.php, (3) /xmlrpc/server.php, and (4) /xmlrpc/api_metaweblog.inc.php.  NOTE: this is a similar vulnerability to CVE-2006-2583.  NOTE: this issue has been disputed by third parties, who state that the DIR_LIBS parameter is defined in an include file before being used

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

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

It affects 1 product.


Products: Nucleus Group Nucleus Cms.

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

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

## Is CVE-2006-3136 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2056](https://insights.sbomify.com/CVE-2004-2056/): SQL injection in n/a (high 7.5)
- [CVE-2006-2583](https://insights.sbomify.com/CVE-2006-2583/): Code injection in n/a (medium 5.1)
- [CVE-2009-0929](https://insights.sbomify.com/CVE-2009-0929/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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