# phpMyAdmin vulnerable to Cross-Site Request Forgery

Advisory record · `GHSA-2p7v-jm8m-g3qq`

- **Identifiers:** `GHSA-2p7v-jm8m-g3qq` · `CVE-2016-5739` · `PKSA-99kf-x3tq-b2v6`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 14 May 2022
- **Updated:** 14 Apr 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 02:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `phpmyadmin/phpmyadmin` (Packagist): affected `>=4.0.10.0, <4.0.10.16 || >=4.4.15.0, <4.4.15.7 || >=4.6.0, <4.6.3`; fixed in `4.0.10.16`, `4.4.15.7`, `4.6.3`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.029, the 87th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 14 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-2p7v-jm8m-g3qq](https://github.com/advisories/GHSA-2p7v-jm8m-g3qq)
- [OSV: GHSA-2p7v-jm8m-g3qq](https://osv.dev/vulnerability/GHSA-2p7v-jm8m-g3qq)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-5739>
- <https://github.com/phpmyadmin/phpmyadmin/commit/1e5716cb96d46efc305381ae0da08e73fe340f05>
- <https://github.com/phpmyadmin/phpmyadmin/commit/2f4950828ec241e8cbdcf13090c2582a6fa620cb>
- <https://github.com/phpmyadmin/phpmyadmin>
- <https://security.gentoo.org/glsa/201701-32>
- <https://web.archive.org/web/20200227223419/http://www.securityfocus.com/bid/91389>
- <https://www.phpmyadmin.net/security/PMASA-2016-28>
- <http://lists.opensuse.org/opensuse-updates/2016-06/msg00113.html>
- <http://lists.opensuse.org/opensuse-updates/2016-06/msg00114.html>
- <http://www.debian.org/security/2016/dsa-3627>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2p7v-jm8m-g3qq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2p7v-jm8m-g3qq/>. Everything for agents: <https://agentprime.io/llms.txt>.
