CVE-2026-64876

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 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.

Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in GeoIP extension - Database-update requests lacked consistent token and Super User checks, this could cause unauthorized updates.

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
3%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 29, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
No patch confirmed yet.
generic

Regular Labs - Extensions for Joomla! - Regular Labs

https://regularlabs.com/

Vendor Advisories for CVE-2026-64876(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 33× 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-07-31 22:13 UTCGHSA enrichment
  2. 2026-07-31 09:38 UTCGHSA enrichment
  3. 2026-07-30 21:08 UTCEG score recompute
  4. 2026-07-30 21:08 UTCGHSA enrichment
  5. 2026-07-30 16:28 UTCEPSS rescore
  6. 2026-07-30 07:38 UTCEG score recompute
  7. 2026-07-30 07:38 UTCGHSA enrichment
  8. 2026-07-30 01:30 UTCEPSS rescore
  9. 2026-07-30 01:30 UTCEPSS rescore
  10. 2026-07-29 18:14 UTCGHSA enrichment
  11. 2026-07-29 05:42 UTCGHSA enrichment
  12. 2026-07-29 05:16 UTCEG score recompute
  13. 2026-07-29 05:16 UTCGHSA enrichment
  14. 2026-07-28 16:45 UTCEG score recompute
  15. 2026-07-28 16:45 UTCGHSA enrichment
  16. 2026-07-28 15:37 UTCEPSS rescore
  17. 2026-07-28 15:32 UTCEG score recompute▲ 8.80
  18. 2026-07-28 15:32 UTCGHSA enrichment
  19. 2026-07-28 15:29 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  20. 2026-07-27 14:14 UTCEPSS rescore
  21. 2026-07-26 03:18 UTCEG score recompute
  22. 2026-07-26 03:18 UTCGHSA enrichment
  23. 2026-07-25 14:18 UTCEPSS rescore
  24. 2026-07-25 14:18 UTCEPSS rescore
  25. 2026-07-24 14:18 UTCEPSS rescore
Show 8 more
  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 16:11 UTCNVD update
  3. 2026-07-23 15:36 UTCMITRE cvelistV5
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 11:51 UTCNVD update
  7. 2026-07-23 09:25 UTCEG score recompute
  8. 2026-07-23 09:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64876?
CVE-2026-64876 is a high vulnerability published on July 23, 2026. Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in GeoIP extension - Database-update requests lacked consistent token and Super User checks, this could cause unauthorized updates.
When was CVE-2026-64876 disclosed?
CVE-2026-64876 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64876 actively exploited?
CVE-2026-64876 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64876?
CVE-2026-64876 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-64876?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64876, 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-64876

Explore →

Is Your Infrastructure Affected by CVE-2026-64876?

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

Start Free Scan →Browse All CVEs