CVE-2026-72558

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An SQL injection vulnerability in CiviCRM through 6.18.alpha1 allows authenticated staff to read the entire database via the contact search RLIKE clause. The clause concatenates a user-supplied value into the SQL query without sanitization. An attacker with staff-level access can exfiltrate all database contents including donor and member records.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

GitHub - civicrm/civicrm-core: CiviCRM (Core Application and Framework) · GitHub

https://github.com/civicrm/civicrm-core

Vendor Advisories for CVE-2026-72558(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 46× 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.

  1. 2026-08-21 03:13 UTCEG score recompute
  2. 2026-08-21 03:13 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:22 UTCGHSA enrichment
  5. 2026-08-20 05:32 UTCGHSA enrichment
  6. 2026-08-19 18:42 UTCEG score recompute
  7. 2026-08-19 18:42 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:22 UTCGHSA enrichment
  10. 2026-08-18 19:11 UTCEG score recompute
  11. 2026-08-18 19:11 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 08:22 UTCGHSA enrichment
  15. 2026-08-17 21:12 UTCEG score recompute
  16. 2026-08-17 21:12 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 10:21 UTCGHSA enrichment
  19. 2026-08-16 23:32 UTCEG score recompute
  20. 2026-08-16 23:32 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 12:42 UTCEG score recompute
  24. 2026-08-16 12:42 UTCGHSA enrichment
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 21 more
  1. 2026-08-16 01:52 UTCGHSA enrichment
  2. 2026-08-15 15:02 UTCGHSA enrichment
  3. 2026-08-15 04:12 UTCEG score recompute
  4. 2026-08-15 04:12 UTCGHSA enrichment
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 17:22 UTCGHSA enrichment
  7. 2026-08-14 06:24 UTCEG score recompute
  8. 2026-08-14 06:24 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 19:34 UTCGHSA enrichment
  11. 2026-08-13 08:44 UTCGHSA enrichment
  12. 2026-08-12 21:54 UTCEG score recompute
  13. 2026-08-12 21:54 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-12 11:05 UTCGHSA enrichment
  16. 2026-08-12 00:15 UTCGHSA enrichment
  17. 2026-08-11 13:25 UTCEG score recompute
  18. 2026-08-11 13:25 UTCGHSA enrichment
  19. 2026-08-11 12:26 UTCEG score recompute
  20. 2026-08-11 11:22 UTCEG score recompute
  21. 2026-08-11 11:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72558?
CVE-2026-72558 is a high vulnerability published on August 11, 2026. An SQL injection vulnerability in CiviCRM through 6.18.alpha1 allows authenticated staff to read the entire database via the contact search RLIKE clause. The clause concatenates a user-supplied value into the SQL query without sanitization. An attacker with staff-level access can exfiltrate all…
When was CVE-2026-72558 disclosed?
CVE-2026-72558 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72558 actively exploited?
CVE-2026-72558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.8% of all scored CVEs.
What is the CVSS score of CVE-2026-72558?
CVE-2026-72558 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-72558?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72558, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72558

Explore →

Is Your Infrastructure Affected by CVE-2026-72558?

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

Start Free Scan →Browse All CVEs