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

> Remote attackers can execute arbitrary code via format string specifiers in MySQL error messages within the PHP mysqli extension.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3qpw-mprx-xfrv

## What is CVE-2006-0200?

CVE-2006-0200 is a critical code injection vulnerability in Php Php, published on 13 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the error-reporting feature in the mysqli extension in PHP 5.1.0 and 5.1.1 might allow remote attackers to execute arbitrary code via format string specifiers in MySQL error messages.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Php Php.

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

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

## Is CVE-2006-0200 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0200 is a critical code injection vulnerability in Php Php, published on 13 Jan 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-0200 in the wild and no public exploit code.

Affected product: Php Php. 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-0200/ (Markdown: https://insights.sbomify.com/CVE-2006-0200/index.md)
```

## Sources

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

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