# CVE-2006-1804: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the sql_query parameter in phpMyAdmin, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1804, GHSA-3j5v-cjrg-phc7

## What is CVE-2006-1804?

CVE-2006-1804 is a high-severity SQL injection vulnerability in Phpmyadmin Phpmyadmin, published on 18 Apr 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in sql.php in phpMyAdmin 2.7.0-pl1 allows remote attackers to execute arbitrary SQL commands via the sql_query parameter.

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

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

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

Upgrade to a fixed version.

## Is CVE-2006-1804 being exploited?

There is no known exploitation of CVE-2006-1804 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-2007-0203](https://insights.sbomify.com/CVE-2007-0203/): Other in n/a (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1804 is a high-severity SQL injection vulnerability in Phpmyadmin Phpmyadmin, published on 18 Apr 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1804 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-2006-1804/ (Markdown: https://insights.sbomify.com/CVE-2006-1804/index.md)
```

## Sources

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

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