CVE-2026-63685

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. 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 - Authorization bypass in DB Replacer extension - Administrator routes and replacement requests did not consistently require Super User permission and a valid token. An unauthorized backend user or CSRF attack could perform database replacements, potentially causing major data corruption or site compromise.

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

Published

July 22, 2026

Last Modified

July 28, 2026

Advisory Details (1)

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

Regular Labs - Extensions for Joomla! - Regular Labs

https://regularlabs.com/

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63685?
CVE-2026-63685 is a high vulnerability published on July 22, 2026. Joomla Extension - regularlabs.com - Authorization bypass in DB Replacer extension - Administrator routes and replacement requests did not consistently require Super User permission and a valid token. An unauthorized backend user or CSRF attack could perform database replacements, potentially…
When was CVE-2026-63685 disclosed?
CVE-2026-63685 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63685 actively exploited?
CVE-2026-63685 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-63685?
CVE-2026-63685 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-63685?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63685, 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-63685

Explore →

Is Your Infrastructure Affected by CVE-2026-63685?

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

Start Free Scan →Browse All CVEs