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

> Remote attackers can execute arbitrary PHP code by overwriting variables via the extract function in blog.php.

- **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:** 20 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qhrq-r9hf-mvc8

## What is CVE-2006-6661?

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

### Official description

Variable overwrite vulnerability in blog.php in PHP-Update 2.7 and earlier allows remote attackers to overwrite arbitrary program variables and execute arbitrary PHP code via multiple vectors that use the extract function, as demonstrated by the (1) f, (2) newmessage, (3) newusername, (4) adminuser, and (5) permission parameters.

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

It affects 1 product.


Products: Php-Update Php-Update.

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

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

## Is CVE-2006-6661 being exploited?

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

Public exploit code:

- PHP-Update 2.7 - 'extract()' Authentication Bypass / Shell Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6878](https://insights.sbomify.com/CVE-2006-6878/): Privilege escalation in n/a (high 7.5)
- [CVE-2006-6880](https://insights.sbomify.com/CVE-2006-6880/): SQL injection in n/a (high 7.5)
- [CVE-2006-6879](https://insights.sbomify.com/CVE-2006-6879/): File upload in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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