phpMyAdmin SSRF in replication

published 2017-07-13 9 y ago modified 2026-06-17 4 mo ago also GHSA-99xj-xqc9-98hr , EUVD-2022-3344

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits: 0; none known

phpMyAdmin 4.0, 4.4 and 4.6 are vulnerable to a weakness where a user with appropriate permissions is able to connect to an arbitrary MySQL server

Patch / fix

fixed in 2 distros 2

packagist phpmyadmin/phpmyadmin 4.0.10.19, 4.4.15.10, 4.6.6
phpmyadmin phpmyadmin 4.0.10.19

debian opensuse

phpmyadmin Debian 14, Debian 13, Debian 12 4:4.6.6-1

debian advisories DEBIAN-CVE-2017-1000017

phpMyAdmin openSUSE Tumbleweed 5.1.1-1.2

opensuse advisories openSUSE-SU-2024:11171-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000017 updated 2025-11-21 cvss 6.5

phpMyAdmin: SSRF in replication

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	phpmyadmin/phpmyadmin	>=4.6, <4.6.6 >=4.4, <4.4.15.10 >=4.0, <4.0.10.19	4.6.6 4.4.15.10 4.0.10.19

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

phpmyadmin.net /security/PMASA-2017-6
web, vendor-advisory
securityfocus.com /bid/95732
vdb-entry, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-1000017
advisory
github.com /phpmyadmin/composer
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary