CVE-2026-76793

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
8.1EG
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.1Exploit: None knownExposed: 0

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

The Firebase Authentication WordPress plugin before 1.7.1 does not require the email address in an authentication token to be verified before matching it to a WordPress account and issuing a session, allowing unauthenticated attackers to log in as any user, including administrators.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 23, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Firebase Authentication < 1.7.1 – Unauthenticated Account Takeover via Firebase Email Claim | CVE 2026-76793 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/0414ef2b-0d97-41c7-9146-f31ace8b66b2/

Vendor Advisories for CVE-2026-76793(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 30× in last 7d / 34× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:55 UTCGHSA enrichment
  3. 2026-08-29 13:30 UTCGHSA enrichment
  4. 2026-08-29 02:01 UTCEG score recompute
  5. 2026-08-29 02:00 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 14:35 UTCGHSA enrichment
  8. 2026-08-28 03:06 UTCGHSA enrichment
  9. 2026-08-27 15:40 UTCEG score recompute
  10. 2026-08-27 15:40 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 04:11 UTCGHSA enrichment
  13. 2026-08-26 16:46 UTCEG score recompute
  14. 2026-08-26 16:45 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 12:53 UTCGHSA enrichment
  17. 2026-08-26 01:28 UTCGHSA enrichment
  18. 2026-08-25 14:03 UTCEG score recompute
  19. 2026-08-25 14:03 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 02:37 UTCGHSA enrichment
  22. 2026-08-24 15:12 UTCEG score recompute
  23. 2026-08-24 15:12 UTCGHSA enrichment
  24. 2026-08-24 14:18 UTCEPSS rescore
  25. 2026-08-24 03:48 UTCEG score recompute
Show 9 more
  1. 2026-08-24 03:48 UTCGHSA enrichment
  2. 2026-08-23 16:23 UTCGHSA enrichment
  3. 2026-08-23 15:36 UTCEG score recompute▲ 8.10
  4. 2026-08-23 15:36 UTCGHSA enrichment
  5. 2026-08-23 15:35 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 06:25 UTCNVD update
  8. 2026-08-22 06:13 UTCEG score recompute
  9. 2026-08-22 06:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76793?
CVE-2026-76793 is a high vulnerability published on August 22, 2026. The Firebase Authentication WordPress plugin before 1.7.1 does not require the email address in an authentication token to be verified before matching it to a WordPress account and issuing a session, allowing unauthenticated attackers to log in as any user, including administrators.
When was CVE-2026-76793 disclosed?
CVE-2026-76793 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76793 actively exploited?
CVE-2026-76793 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 72.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76793?
CVE-2026-76793 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-76793?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76793, 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-76793

Explore →

Is Your Infrastructure Affected by CVE-2026-76793?

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

Start Free Scan →Browse All CVEs