# CVE-2008-1149: SQL injection in n/a

> Attackers can exploit parameter handling flaws to perform SQL injection and CSRF attacks, potentially compromising database integrity and confidentiality.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1149, GHSA-p842-vv7g-4q9v

## What is CVE-2008-1149?

CVE-2008-1149 is a medium-severity SQL injection vulnerability in Phpmyadmin Phpmyadmin, published on 4 Mar 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

phpMyAdmin before 2.11.5 accesses $_REQUEST to obtain some parameters instead of $_GET and $_POST, which allows attackers in the same domain to override certain variables and conduct SQL injection and Cross-Site Request Forgery (CSRF) attacks by using crafted cookies.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2008-1149?

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

## How do I fix CVE-2008-1149?

Upgrade to a fixed version.

## Is CVE-2008-1149 being exploited?

There is no known exploitation of CVE-2008-1149 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-2008-1149 and fix it if it is affected.

What it is: CVE-2008-1149 is a medium-severity SQL injection vulnerability in Phpmyadmin Phpmyadmin, published on 4 Mar 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-1149 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-2008-1149/ (Markdown: https://insights.sbomify.com/CVE-2008-1149/index.md)
```

## Sources

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

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