CVE-2020-26935

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 67% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
CISA-KEV: Not listedEPSS PROB: 67%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL injection vulnerability was discovered in how phpMyAdmin processes SQL statements in the search feature. An attacker could use this flaw to inject malicious SQL in to a query.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation67% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
67%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack 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 (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 10, 2020

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Oct 4, 2026
Patch available.
generic

PMASA-2020-6 · phpMyAdmin

https://www.phpmyadmin.net/security/PMASA-2020-6/
generic

phpMyAdmin: Multiple vulnerabilities (GLSA 202101-35) — Gentoo security

https://security.gentoo.org/glsa/202101-35
generic

[SECURITY] Fedora 32 Update: phpMyAdmin-5.0.3-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TNLGHVDNAEZEGRTUESSSQFM7MZTHIDQ5/
generic

[SECURITY] Fedora 31 Update: phpMyAdmin-5.0.3-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PXK37YEHSDYCIPQSYEMN2OFTP2ZLM7DO/
generic

[SECURITY] Fedora 33 Update: phpMyAdmin-5.0.3-1.fc33 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FHST4E5IJG7IKZTTW3R6MEZPVHJZ472K/
generic Patch Available

[SECURITY] [DLA 2413-1] phpmyadmin security update

https://lists.debian.org/debian-lts-announce/2020/10/msg00024.html
generic

Checkmarx Advisory

https://advisory.checkmarx.net/advisory/CX-2020-4281

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphpmyadmin (4:4.6.6-5ubuntu0.5) @ bionic2026-05-23ubuntu
ubuntuphpmyadmin (4:4.5.4.1-2ubuntu2.1+esm6) @ xenial2026-05-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.9.7+dfsg1-1: fixed in 4:4.9.7+dfsg1-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.9.7+dfsg1-1: fixed in 4:4.9.7+dfsg1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.9.7+dfsg1-1: fixed in 4:4.9.7+dfsg1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin—
  • every version up to 4:4.9.7+dfsg1-1: fixed in 4:4.9.7+dfsg1-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin4:4.6.6-4, 4:4.6.6-4+deb9u1
  • every version up to 4:4.6.6-4+deb9u2: fixed in 4:4.6.6-4+deb9u2
—
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
phpmyadmin/phpmyadmin5.0.0, 5.0.0.1, 5.0.1, 5.0.2
  • 4.9.0 up to 4.9.6: fixed in 4.9.6
  • 5.0.0 up to 5.0.3: fixed in 5.0.3
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 107 total refreshes for this CVE.

  1. 2026-10-03 14:22 UTCEPSS rescore
  2. 2026-09-30 15:16 UTCEG score recompute
  3. 2026-09-30 14:59 UTCEPSS rescore
  4. 2026-09-27 13:41 UTCEPSS rescore
  5. 2026-09-26 15:54 UTCEPSS rescore
  6. 2026-09-26 15:54 UTCEPSS rescore
  7. 2026-09-24 14:00 UTCEPSS rescore
  8. 2026-09-22 14:43 UTCEPSS rescore
  9. 2026-09-21 20:28 UTCEPSS rescore
  10. 2026-09-20 20:11 UTCEPSS rescore
  11. 2026-09-20 01:15 UTCOSV refresh
  12. 2026-09-19 15:37 UTCEPSS rescore
  13. 2026-09-18 19:23 UTCEPSS rescore
  14. 2026-09-17 19:22 UTCEPSS rescore
  15. 2026-09-16 14:04 UTCEPSS rescore
  16. 2026-09-15 03:06 UTCEPSS rescore
  17. 2026-09-13 16:43 UTCEPSS rescore
  18. 2026-09-11 09:32 UTCEPSS rescore
  19. 2026-09-06 13:44 UTCEPSS rescore
  20. 2026-09-05 15:24 UTCEPSS rescore
  21. 2026-09-04 13:57 UTCEPSS rescore
  22. 2026-09-04 05:03 UTCEPSS rescore
  23. 2026-09-02 14:08 UTCEPSS rescore
  24. 2026-09-01 04:29 UTCOSV refresh
  25. 2026-08-30 19:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 01:18 UTCEPSS rescore
  2. 2026-08-26 14:42 UTCEPSS rescore
  3. 2026-08-25 13:45 UTCEPSS rescore
  4. 2026-08-21 23:45 UTCEPSS rescore
  5. 2026-08-20 22:52 UTCEPSS rescore
  6. 2026-08-19 17:00 UTCEPSS rescore
  7. 2026-08-17 13:43 UTCEPSS rescore
  8. 2026-08-16 02:11 UTCEPSS rescore
  9. 2026-08-15 04:07 UTCOSV refresh
  10. 2026-08-15 01:26 UTCEPSS rescore
  11. 2026-08-13 21:57 UTCEPSS rescore
  12. 2026-08-12 13:47 UTCEPSS rescore
  13. 2026-08-08 16:33 UTCEPSS rescore
  14. 2026-08-07 16:23 UTCEPSS rescore
  15. 2026-08-06 13:43 UTCEPSS rescore
  16. 2026-08-02 02:23 UTCEPSS rescore
  17. 2026-07-30 16:25 UTCEPSS rescore
  18. 2026-07-30 16:21 UTCOSV refresh
  19. 2026-07-30 01:27 UTCEPSS rescore
  20. 2026-07-28 15:33 UTCEPSS rescore
  21. 2026-07-26 14:51 UTCEPSS rescore
  22. 2026-07-24 14:14 UTCEPSS rescore
  23. 2026-07-23 14:15 UTCEPSS rescore
  24. 2026-07-23 14:15 UTCEPSS rescore
  25. 2026-07-23 01:52 UTCEG score recompute
  26. 2026-07-22 22:38 UTCEG score recompute
  27. 2026-07-22 14:05 UTCEPSS rescore
  28. 2026-07-21 15:22 UTCEPSS rescore
  29. 2026-07-21 15:22 UTCEPSS rescore
  30. 2026-07-20 17:04 UTCEPSS rescore
  31. 2026-07-20 17:04 UTCEPSS rescore
  32. 2026-07-19 14:28 UTCEPSS rescore
  33. 2026-07-19 14:28 UTCEPSS rescore
  34. 2026-07-16 16:59 UTCEPSS rescore
  35. 2026-07-15 16:55 UTCEPSS rescore
  36. 2026-07-15 16:55 UTCEPSS rescore
  37. 2026-07-15 01:57 UTCEPSS rescore
  38. 2026-07-13 22:27 UTCEPSS rescore
  39. 2026-07-13 22:27 UTCEPSS rescore
  40. 2026-07-13 06:10 UTCEPSS rescore
  41. 2026-07-13 06:10 UTCEPSS rescore
  42. 2026-07-13 01:37 UTCOSV refresh
  43. 2026-07-12 05:44 UTCEPSS rescore
  44. 2026-07-11 08:25 UTCEPSS rescore
  45. 2026-07-11 08:25 UTCEPSS rescore
  46. 2026-07-09 19:07 UTCEPSS rescore
  47. 2026-07-08 15:12 UTCEPSS rescore
  48. 2026-06-30 23:20 UTCEPSS rescore
  49. 2026-06-30 23:20 UTCEPSS rescore
  50. 2026-06-27 03:06 UTCEPSS rescore
  51. 2026-06-27 03:06 UTCEPSS rescore
  52. 2026-06-25 13:48 UTCEPSS rescore
  53. 2026-06-24 14:03 UTCEPSS rescore
  54. 2026-06-24 14:03 UTCEPSS rescore
  55. 2026-06-24 10:50 UTCOSV refresh
  56. 2026-06-23 21:31 UTCEPSS rescore
  57. 2026-06-23 21:31 UTCEPSS rescore
  58. 2026-06-19 19:24 UTCEPSS rescore
  59. 2026-06-19 19:23 UTCEPSS rescore
  60. 2026-06-17 17:50 UTCEPSS rescore
  61. 2026-06-16 17:50 UTCEPSS rescore
  62. 2026-06-15 17:46 UTCEPSS rescore
  63. 2026-06-14 23:15 UTCEPSS rescore
  64. 2026-06-13 22:58 UTCEPSS rescore
  65. 2026-06-10 22:16 UTCEPSS rescore
  66. 2026-06-10 13:20 UTCEPSS rescore
  67. 2026-06-07 15:21 UTCOSV refresh
  68. 2026-06-05 22:45 UTCEPSS rescore
  69. 2026-06-05 22:45 UTCEPSS rescore
  70. 2026-06-05 06:08 UTCEPSS rescore
  71. 2026-06-05 06:08 UTCEPSS rescore
  72. 2026-06-04 13:10 UTCEPSS rescore
  73. 2026-06-04 13:10 UTCEPSS rescore
  74. 2026-06-02 20:11 UTCEPSS rescore
  75. 2026-06-02 20:11 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2020/CVE-2020-26935.yaml
    First seen Jan 1, 2020

    phpMyAdmin < 5.0.3 - SQL Injection

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2020-26935?
CVE-2020-26935 is a critical vulnerability published on October 10, 2020. An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL injection vulnerability was discovered in how phpMyAdmin processes SQL statements in the search feature. An attacker could use this flaw to inject malicious SQL in to a query.
When was CVE-2020-26935 disclosed?
CVE-2020-26935 was first published on October 10, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26935 actively exploited?
CVE-2020-26935 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-26935?
CVE-2020-26935 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-26935?
A fix for CVE-2020-26935 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-26935

Explore →

Is Your Infrastructure Affected by CVE-2020-26935?

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

Book a Demo →Browse All CVEs