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

> Remote attackers can execute arbitrary PHP code via eval injection in PHPLib cookies if index.php3 is accessible.

- **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:** 25 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fq4g-p58q-8f6g

## What is CVE-2006-0887?

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

### Official description

Eval injection vulnerability in sessions.inc in PHP Base Library (PHPLib) before 7.4a, when index.php3 from the PHPLib distribution is available on the server, allows remote attackers to execute arbitrary PHP code by including a base64-encoded representation of the code in a cookie.  NOTE: this description was significantly updated on 20060605 to reflect new details after an initial vague advisory.

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

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

It affects 1 product.


Products: Phplib Team Phplib.

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

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

## Is CVE-2006-0887 being exploited?

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

Public exploit code:

- PHPLib < 7.4 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1370](https://insights.sbomify.com/CVE-2001-1370/): Code injection in n/a (critical 10.0)
- [CVE-2006-2826](https://insights.sbomify.com/CVE-2006-2826/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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