CVE-2026-19714
Auth bypass in Simple JWT Login plugin lets attackers log in as any user via Google tokens.
Is CVE-2026-19714 being exploited?
Not confirmed. CVE-2026-19714 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-19714?
CVE-2026-19714 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-19714?
Yes. A fix has been recorded for CVE-2026-19714. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19714 affect?
CVE-2026-19714 affects Simple JWT Login WordPress plugin <3.6.8 (Google sign-in enabled), WordPress sites using that plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19714?
Update plugin to >=3.6.8 or disable Google sign-in until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can authenticate as any user (including admin) by supplying a Google ID token with unvalidated audience.
Immediate action required
- affected< 3.6.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.