# CVE-2008-5621: Cross-site request forgery in n/a

> Remote attackers can trick administrators into performing unauthorized actions via CSRF, potentially leading to SQL injection and arbitrary code execution.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2008-5622, DEBIAN-CVE-2008-5621, DSA-1723-1, GHSA-427m-jx2h-q45m

## What is CVE-2008-5621?

CVE-2008-5621 is a medium-severity vulnerability in Phpmyadmin Phpmyadmin, published on 17 Dec 2008. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in phpMyAdmin 2.11.x before 2.11.9.4 and 3.x before 3.1.1.0 allows remote attackers to perform unauthorized actions as the administrator via a link or IMG tag to tbl_structure.php with a modified table parameter.  NOTE: other unspecified pages are also reachable, but they have the same root cause.  NOTE: this can be leveraged to conduct SQL injection attacks and execute arbitrary code.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

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

Upgrade to a fixed version.

## Is CVE-2008-5621 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5621 exists.

Public exploit code:

- phpMyAdmin 3.1.0 - Cross-Site Request Forgery / SQL Injection (exploitdb)

## 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-5621 and fix it if it is affected.

What it is: CVE-2008-5621 is a medium-severity vulnerability in Phpmyadmin Phpmyadmin, published on 17 Dec 2008. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5621 exists.

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-5621/ (Markdown: https://insights.sbomify.com/CVE-2008-5621/index.md)
```

## Sources

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

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