Skip to content
Fencer Intel
medium 6.1

CVE-2016-5701 json

phpMyAdmin vulnerable to Cross-site Scripting

published 2016-07-03 10 y ago modified 2026-06-17 4 mo ago also GHSA-rh74-5835-jpxp , EUVD-2016-6643

cvss
6.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

setup/frames/index.inc.php in phpMyAdmin 4.0.10.x before 4.0.10.16, 4.4.15.x before 4.4.15.7, and 4.6.x before 4.6.3 allows remote attackers to conduct BBCode injection attacks against HTTP sessions via a crafted URI.

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.0.10.16, 4.4.15.7, 4.6.3
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.6.3-1

debian advisories DEBIAN-CVE-2016-5701

  • phpMyAdmin openSUSE Tumbleweed 4.6.5.2-1.1

opensuse advisories openSUSE-SU-2024:10054-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-2016-5701 updated

phpMyAdmin: 4.6.3, 4.4.15.7 and 4.0.10.16 security releases

  • 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.54% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.0.10.0, <4.0.10.16
>=4.4.15.0, <4.4.15.7
>=4.6.0, <4.6.3
4.0.10.16
4.4.15.7
4.6.3

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel 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.