# CVE-2007-0203: Other in n/a

> Multiple unspecified vulnerabilities in phpMyAdmin allow attackers to potentially compromise the database administration interface.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 11 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0203, GHSA-7g9j-m92v-995c

## What is CVE-2007-0203?

CVE-2007-0203 is a critical vulnerability in Phpmyadmin Phpmyadmin, published on 11 Jan 2007. It can be exploited over the network.

### Official description

Multiple unspecified vulnerabilities in phpMyAdmin before 2.9.2-rc1 have unknown impact and attack vectors.

## Which versions are affected by CVE-2007-0203?

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

## How do I fix CVE-2007-0203?

Upgrade to a fixed version.

## Is CVE-2007-0203 being exploited?

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

## Other vulnerabilities in Phpmyadmin Phpmyadmin

- [CVE-2008-7251](https://insights.sbomify.com/CVE-2008-7251/): Misconfiguration in n/a (critical 10.0)
- [CVE-2008-7252](https://insights.sbomify.com/CVE-2008-7252/): phpMyAdmin unsafely handles temporary files (critical 10.0)
- [CVE-2004-1147](https://insights.sbomify.com/CVE-2004-1147/): Command injection in n/a (critical 10.0)
- [CVE-2020-22452](https://insights.sbomify.com/CVE-2020-22452/): phpmyadmin contains SQL Injection vulnerability (critical 9.8)
- [CVE-2019-11768](https://insights.sbomify.com/CVE-2019-11768/): phpMyAdmin SQL injection in Designer feature (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0203 and fix it if it is affected.

What it is: CVE-2007-0203 is a critical vulnerability in Phpmyadmin Phpmyadmin, published on 11 Jan 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-0203 in the wild and no public exploit code.

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

## Sources

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

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