# CVE-2005-4450: Cross-site request forgery in n/a

> Remote attackers can trick logged-in users into performing unauthorized actions via CSRF in phpMyAdmin, potentially escalating privileges or modifying data.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Dec 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-282v-8gf3-6m78

## What is CVE-2005-4450?

CVE-2005-4450 is a high-severity vulnerability in Phpmyadmin Phpmyadmin, published on 21 Dec 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in phpMyAdmin 2.7.0 allows remote attackers to perform unauthorized actions as a logged-in user via a link or IMG tag to server_privileges.php, as demonstrated using the dbname and checkprivs parameters.  NOTE: the provenance of this issue is unknown, although third parties imply that it is related to the disclosure of CVE-2005-4349, which was labeled as SQL injection but disputed.

## Which versions are affected by CVE-2005-4450?

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

## How do I fix CVE-2005-4450?

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

## Is CVE-2005-4450 being exploited?

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

What it is: CVE-2005-4450 is a high-severity vulnerability in Phpmyadmin Phpmyadmin, published on 21 Dec 2005. 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-2005-4450 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-2005-4450/ (Markdown: https://insights.sbomify.com/CVE-2005-4450/index.md)
```

## Sources

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

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