Skip to content
Fencer Intel
high 7.5

CVE-2016-1927 json

phpMyAdmin Cryptographic Vulnerability

published 2016-02-20 10 y ago modified 2026-06-17 4 mo ago also GHSA-4gmg-gwjh-3mmr , EUVD-2022-2379

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

Summary

The suggestPassword function in js/functions.js in phpMyAdmin 4.0.x before 4.0.10.13, 4.4.x before 4.4.15.3, and 4.5.x before 4.5.4 relies on the Math.random JavaScript function, which makes it easier for remote attackers to guess passwords via a brute-force approach.

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.0.10.13, 4.4.15.3, 4.5.4
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.5.4-1

debian advisories DEBIAN-CVE-2016-1927

  • 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-1927 updated cvss 2.6

phpMyAdmin: Insecure password generation in JavaScript (PMASA-2016-4)

  • 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

2.69% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.0.0, <4.0.10.13
>=4.4.0, <4.4.15.3
>=4.5.0, <4.5.4
4.0.10.13
4.4.15.3
4.5.4

Classification

Weakness
  • CWE-254 7PK - Security Features
  • CWE-255 Credentials Management Errors

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.