Skip to content
Fencer Intel
medium 4.3

CVE-2014-6300 json

phpMyAdmin micro history Implementation XSS Vulnerability

published 2014-11-08 12 y ago modified 2026-06-17 4 mo ago also GHSA-6wfj-2mw7-p5cg , EUVD-2022-2869

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

Cross-site scripting (XSS) vulnerability in the micro history implementation in phpMyAdmin 4.0.x before 4.0.10.3, 4.1.x before 4.1.14.4, and 4.2.x before 4.2.8.1 allows remote attackers to inject arbitrary web script or HTML, and consequently conduct a cross-site request forgery (CSRF) attack to create a root account, via a crafted URL, related to js/ajax.js.

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.0.10.3, 4.1.14.4, 4.2.8.1
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.2.8.1-1

debian advisories DEBIAN-CVE-2014-6300

  • 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-2014-6300 updated cvss 4.3

phpMyAdmin: XSS flaw possibly leading to root account creation (PMASA-2014-10)

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

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.0.0, <4.0.10.3
>=4.1.0, <4.1.14.4
>=4.2.0, <4.2.8.1
4.0.10.3
4.1.14.4
4.2.8.1

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.