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

> Remote attackers can execute arbitrary PHP code by uploading malicious files via the NukeAI module in PHP-Nuke.

- **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:** 4 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2923-cx8w-xvxh

## What is CVE-2006-6255?

CVE-2006-6255 is a high-severity code injection vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Direct static code injection vulnerability in util.php in the NukeAI 0.0.3 Beta module for PHP-Nuke, aka Program E is an AIML chatterbot, allows remote attackers to upload and execute arbitrary PHP code via a filename with a .php extension in the filename parameter and code in the moreinfo parameter, which is saved to a filename under descriptions/, which is accessible via a direct request.

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

It affects 1 product.


Products: Nukeai Nukeai.

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

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

## Is CVE-2006-6255 being exploited?

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

Public exploit code:

- PHP-Nuke NukeAI Module 3b - 'util.php' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6202](https://insights.sbomify.com/CVE-2006-6202/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6255 is a high-severity code injection vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6255 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-6255/ (Markdown: https://insights.sbomify.com/CVE-2006-6255/index.md)
```

## Sources

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

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