CVE-2026-19714

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.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: 9.1Exploit: Elevated riskExposed: 0

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

The Simple JWT Login WordPress plugin before 3.6.8 does not validate the audience of the Google identity tokens it accepts, allowing unauthenticated users to authenticate as any user whose email address such a token carries, up to and including an administrator. Every site with the Simple JWT Login WordPress plugin before 3.6.8's Google sign-in enabled is affected.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (1)

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

Simple JWT Login < 3.6.8 – Unauthenticated Account Takeover via Missing Google id_token Audience Validation | CVE 2026-19714 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/dc6e54eb-d856-484b-88c1-b3e04a37669d/

Vendor Advisories for CVE-2026-19714(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 38× in last 7d / 38× 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 06:56 UTCGHSA enrichment
  2. 2026-08-21 03:04 UTCGHSA enrichment
  3. 2026-08-20 23:12 UTCEG score recompute
  4. 2026-08-20 23:12 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 19:21 UTCGHSA enrichment
  7. 2026-08-20 15:29 UTCGHSA enrichment
  8. 2026-08-20 11:36 UTCGHSA enrichment
  9. 2026-08-20 07:44 UTCGHSA enrichment
  10. 2026-08-20 03:53 UTCGHSA enrichment
  11. 2026-08-20 00:01 UTCGHSA enrichment
  12. 2026-08-19 20:08 UTCEG score recompute
  13. 2026-08-19 20:08 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 16:15 UTCGHSA enrichment
  16. 2026-08-19 12:16 UTCGHSA enrichment
  17. 2026-08-19 08:25 UTCGHSA enrichment
  18. 2026-08-19 04:33 UTCGHSA enrichment
  19. 2026-08-19 00:42 UTCGHSA enrichment
  20. 2026-08-18 20:50 UTCGHSA enrichment
  21. 2026-08-18 16:59 UTCEG score recompute
  22. 2026-08-18 16:59 UTCGHSA enrichment
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-18 12:11 UTCGHSA enrichment
  25. 2026-08-18 08:14 UTCGHSA enrichment
Show 13 more
  1. 2026-08-18 04:18 UTCGHSA enrichment
  2. 2026-08-18 00:24 UTCEG score recompute
  3. 2026-08-18 00:24 UTCGHSA enrichment
  4. 2026-08-17 20:29 UTCGHSA enrichment
  5. 2026-08-17 20:11 UTCEG score recompute▲ 9.10
  6. 2026-08-17 20:11 UTCGHSA enrichment
  7. 2026-08-17 20:09 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 06:30 UTCGHSA enrichment
  11. 2026-08-16 06:30 UTCNVD update
  12. 2026-08-16 06:10 UTCEG score recompute
  13. 2026-08-16 06:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19714?
CVE-2026-19714 is a critical vulnerability published on August 16, 2026. The Simple JWT Login WordPress plugin before 3.6.8 does not validate the audience of the Google identity tokens it accepts, allowing unauthenticated users to authenticate as any user whose email address such a token carries, up to and including an administrator. Every site with the Simple JWT Login…
When was CVE-2026-19714 disclosed?
CVE-2026-19714 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19714 actively exploited?
CVE-2026-19714 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 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-19714?
CVE-2026-19714 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19714, 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-19714

Explore →

Is Your Infrastructure Affected by CVE-2026-19714?

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

Start Free Scan →Browse All CVEs