# phpMyAdmin CSRF Vulnerability

Advisory record · `GHSA-mfr9-pcm3-6mwc`

- **Identifiers:** `GHSA-mfr9-pcm3-6mwc` · `CVE-2019-12616` · `PKSA-61t2-8dhb-6pfx`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 24 May 2022
- **Updated:** 17 Feb 2024
- **Reviewed by a person:** No

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

## Affected packages

- `phpmyadmin/phpmyadmin` (Packagist): affected `<4.9.0`; fixed in `4.9.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> phpMyAdmin versions before 4.9.0 are vulnerable to cross-site request forgery. An attacker can trick a logged-in user into sending a request, for example through a crafted image tag on another page, which may cause database statements such as INSERT or DELETE to run against the victim's phpMyAdmin database. Upgrade to phpMyAdmin 4.9.0 or later.

Written 4 Nov 2026.

## 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

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

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

## Timeline

- 31 Oct 2026, 14:30 UTC: First seen by agentprime
- 31 Oct 2026, 14:30 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mfr9-pcm3-6mwc)

## Sources

- [GitHub Advisory Database: GHSA-mfr9-pcm3-6mwc](https://github.com/advisories/GHSA-mfr9-pcm3-6mwc)
- [OSV: GHSA-mfr9-pcm3-6mwc](https://osv.dev/vulnerability/GHSA-mfr9-pcm3-6mwc)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-12616>
- <https://github.com/phpmyadmin/phpmyadmin/commit/015c404038c44279d95b6430ee5a0dddc97691ec>
- <https://packetstormsecurity.com/files/153251/phpMyAdmin-4.8-Cross-Site-Request-Forgery.html>
- <https://www.phpmyadmin.net/security/PMASA-2019-4>

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-mfr9-pcm3-6mwc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mfr9-pcm3-6mwc/>. Everything for agents: <https://agentprime.io/llms.txt>.
