CVE-2016-5734

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2016-6669 (ENISA EUVD) · GHSA-rv57-479x-x4qv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 92%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the preg_replace e (aka eval) modifier, which might allow remote attackers to execute arbitrary PHP code via a crafted string, as demonstrated by the table search-and-replace implementation.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
81
EG Risk 81/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation92% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
92%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
92% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 3, 2016

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit.
Web page

phpMyAdmin: Multiple vulnerabilities (GLSA 201701-32) — Gentoo security

https://security.gentoo.org/glsa/201701-32
GitHub commit Patch Available

commit 4bcc606225f1 (phpmyadmin/phpmyadmin)

Patch available: phpmyadmin/phpmyadmin RELEASE_4_8_4 (contains commit 4bcc606225f1)

https://github.com/phpmyadmin/phpmyadmin/commit/4bcc606225f15bac0b07780e74f667f6ac283da7
GitHub commit Patch Available

commit 1cc7466db3a0 (phpmyadmin/phpmyadmin)

Patch available: phpmyadmin/phpmyadmin RELEASE_4_8_4 (contains commit 1cc7466db3a0)

https://github.com/phpmyadmin/phpmyadmin/commit/1cc7466db3a05e95fe57a6702f41773e6829d54b
Web page

PMASA-2016-27 · phpMyAdmin

https://www.phpmyadmin.net/security/PMASA-2016-27/
Web page

phpMyAdmin 4.6.2 - (Authenticated) Remote Code Execution - PHP webapps Exploit

https://www.exploit-db.com/exploits/40185/
Web page

CVE-2016-5734 - PSIRT.COM

http://www.securityfocus.com/bid/91387

Vendor Advisories for CVE-2016-5734(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerphpmyadmin/phpmyadmin @ 4.6.3 (fixes >= 4.6.0, < 4.6.3)—ghsa
composerphpmyadmin/phpmyadmin @ 4.0.10.16 (fixes >= 4.0.10.0, < 4.0.10.16)—ghsa
composerphpmyadmin/phpmyadmin @ 4.4.15.7 (fixes >= 4.4.15.0, < 4.4.15.7)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.6.3-1: fixed in 4:4.6.3-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.6.3-1: fixed in 4:4.6.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.6.3-1: fixed in 4:4.6.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.6.3-1: fixed in 4:4.6.3-1
—
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin/phpmyadmin4.0.10.1 ... 4.0.10.9 (9 versions)
  • 4.0.10.0 up to 4.0.10.16: fixed in 4.0.10.16
  • 4.4.15.0 up to 4.4.15.7: fixed in 4.4.15.7
  • 4.6.0 up to 4.6.3: fixed in 4.6.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 159 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:51 UTCEchelonGraph re-scored
  2. 2026-11-21 16:51 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  4. 2026-11-20 16:28 UTCEPSS rescoreEPSS 92% · 99th percentile
  5. 2026-11-20 14:42 UTCEchelonGraph re-scored
  6. 2026-11-20 14:42 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-19 12:33 UTCEchelonGraph re-scored
  8. 2026-11-19 12:33 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-18 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  10. 2026-11-18 10:24 UTCEchelonGraph re-scored
  11. 2026-11-18 10:24 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-17 08:05 UTCEchelonGraph re-scored
  13. 2026-11-17 08:05 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-16 16:34 UTCEPSS rescoreEPSS 92% · 99th percentile
  15. 2026-11-16 05:55 UTCEchelonGraph re-scored
  16. 2026-11-16 05:55 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-15 16:35 UTCEPSS rescoreEPSS 81% · 99th percentile
  18. 2026-11-15 02:54 UTCEchelonGraph re-scored
  19. 2026-11-15 02:54 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-14 00:44 UTCEchelonGraph re-scored
  21. 2026-11-14 00:44 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-13 16:36 UTCEPSS rescoreEPSS 81% · 99th percentile
  23. 2026-11-12 22:34 UTCEchelonGraph re-scored
  24. 2026-11-12 22:34 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-11-11 19:58 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-11 19:58 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-11 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
  3. 2026-11-10 17:48 UTCEchelonGraph re-scored
  4. 2026-11-10 17:48 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-10 16:30 UTCEPSS rescoreEPSS 81% · 99th percentile
  6. 2026-11-09 15:39 UTCEchelonGraph re-scored
  7. 2026-11-09 15:39 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-08 13:30 UTCEchelonGraph re-scored
  9. 2026-11-08 13:30 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-07 11:20 UTCEchelonGraph re-scored
  11. 2026-11-07 11:20 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-06 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
  13. 2026-11-06 09:10 UTCEchelonGraph re-scored
  14. 2026-11-06 09:10 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-05 07:01 UTCEchelonGraph re-scored
  16. 2026-11-05 07:01 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-04 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  18. 2026-11-04 04:51 UTCEchelonGraph re-scored
  19. 2026-11-04 04:51 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-03 16:33 UTCEPSS rescoreEPSS 81% · 99th percentile
  21. 2026-11-03 02:41 UTCEchelonGraph re-scored
  22. 2026-11-03 02:41 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-02 11:55 UTCOSV refresh
  24. 2026-11-02 00:32 UTCEchelonGraph re-scored
  25. 2026-11-02 00:31 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-11-01 08:47 UTCGHSA enrichmentGHSA-rv57-479x-x4qv · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-11-01 08:47 UTCEchelonGraph re-scored
  28. 2026-10-31 22:22 UTCEchelonGraph re-scored
  29. 2026-10-30 20:09 UTCEchelonGraph re-scored
  30. 2026-10-30 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  31. 2026-10-29 17:59 UTCEchelonGraph re-scored
  32. 2026-10-28 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  33. 2026-10-28 15:47 UTCEchelonGraph re-scored
  34. 2026-10-27 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  35. 2026-10-27 13:38 UTCEchelonGraph re-scored
  36. 2026-10-25 19:45 UTCEchelonGraph re-scored
  37. 2026-10-25 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  38. 2026-10-25 08:48 UTCEchelonGraph re-scored
  39. 2026-10-24 06:38 UTCEchelonGraph re-scored
  40. 2026-10-23 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  41. 2026-10-23 04:27 UTCEchelonGraph re-scored
  42. 2026-10-22 02:18 UTCEchelonGraph re-scored
  43. 2026-10-21 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  44. 2026-10-21 00:09 UTCEchelonGraph re-scored
  45. 2026-10-19 21:57 UTCEchelonGraph re-scored
  46. 2026-10-18 19:40 UTCEchelonGraph re-scored
  47. 2026-10-18 10:48 UTCEchelonGraph re-scored
  48. 2026-10-17 17:29 UTCEchelonGraph re-scored
  49. 2026-10-17 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  50. 2026-10-16 15:18 UTCEchelonGraph re-scored
  51. 2026-10-15 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  52. 2026-10-15 13:06 UTCEchelonGraph re-scored
  53. 2026-10-14 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  54. 2026-10-14 08:16 UTCEchelonGraph re-scored
  55. 2026-10-12 20:41 UTCEchelonGraph re-scored
  56. 2026-10-12 01:05 UTCEchelonGraph re-scored
  57. 2026-10-10 19:55 UTCEPSS rescoreEPSS 81% · 99th percentile
  58. 2026-10-07 23:40 UTCEPSS rescoreEPSS 81% · 99th percentile
  59. 2026-10-06 15:11 UTCEPSS rescoreEPSS 81% · 99th percentile
  60. 2026-10-03 21:28 UTCOSV refresh
  61. 2026-09-30 14:58 UTCEPSS rescoreEPSS 81% · 99th percentile
  62. 2026-09-30 09:14 UTCEchelonGraph re-scored
  63. 2026-09-24 13:59 UTCEPSS rescoreEPSS 81% · 99th percentile
  64. 2026-09-18 19:22 UTCEPSS rescoreEPSS 81% · 99th percentile
  65. 2026-09-17 19:22 UTCEPSS rescoreEPSS 81% · 99th percentile
  66. 2026-09-16 05:05 UTCEPSS rescoreEPSS 81% · 99th percentile
  67. 2026-09-14 11:20 UTCOSV refresh
  68. 2026-09-12 14:55 UTCEPSS rescoreEPSS 81% · 99th percentile
  69. 2026-09-10 09:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  70. 2026-09-04 13:56 UTCEPSS rescoreEPSS 81% · 99th percentile
  71. 2026-09-01 03:31 UTCEPSS rescoreEPSS 81% · 99th percentile
  72. 2026-08-28 21:35 UTCEPSS rescoreEPSS 77% · 99th percentile
  73. 2026-08-26 14:41 UTCEPSS rescoreEPSS 81% · 99th percentile
  74. 2026-08-26 12:32 UTCOSV refresh
  75. 2026-08-19 16:59 UTCEPSS rescoreEPSS 81% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/phpmyadmin_null_termination_exec✓ verified
    Published Jun 18, 2018

    phpMyAdmin Authenticated Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2016/CVE-2016-5734.yaml
    Recorded Nov 16, 2026

    phpMyAdmin 4.0.x/4.4.x/4.6.x - Authenticated Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-40185
    Published Jul 29, 2016

    phpMyAdmin 4.6.2 - (Authenticated) Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2016-5734?
CVE-2016-5734 is a critical-severity vulnerability; its CVE record was published on July 3, 2016. phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the preg_replace e (aka eval) modifier, which might allow remote attackers to execute arbitrary PHP code via a crafted string, as demonstrated by the table…
When was CVE-2016-5734 made public?
CVE-2016-5734 was made public on June 23, 2016: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 3, 2016. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2016-5734 actively exploited?
CVE-2016-5734 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-5734?
CVE-2016-5734 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-5734?
A fix for CVE-2016-5734 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-5734 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-5734

Explore →

Is Your Infrastructure Affected by CVE-2016-5734?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.