PatchSiren cyber security CVE debrief
CVE-2026-19714 Simple JWT Login CVE debrief
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.
- Vendor
- Simple JWT Login
- Product
- Simple JWT Login WordPress plugin
- CVSS
- CRITICAL 9.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-16
- Original CVE updated
- 2026-08-26
- Advisory published
- 2026-08-16
- Advisory updated
- 2026-08-26
Who should care
Site administrators using the Simple JWT Login WordPress plugin, especially those with Google sign-in enabled, should be aware of this critical vulnerability. Immediate action is required to prevent potential exploitation.
Technical summary
The Simple JWT Login WordPress plugin before version 3.6.8 does not properly validate the audience claim of Google identity tokens used for authentication. This oversight allows an attacker to authenticate as any user whose email address is present in a valid token, including administrators. The plugin's failure to validate the audience claim effectively bypasses authentication mechanisms, granting unauthorized access to sensitive areas of the site. This vulnerability is particularly severe because it requires no prior authentication or authorization, and it can be exploited by unauthenticated users.
Defensive priority
Immediate attention is required due to the critical severity of this vulnerability, which allows unauthenticated users to authenticate as any user, including administrators.
Recommended defensive actions
- Update the Simple JWT Login WordPress plugin to version 3.6.8 or later
- Disable Google sign-in on affected sites until the update can be applied
- Monitor authentication logs for suspicious activity
- Consider implementing additional security measures, such as two-factor authentication
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The vulnerability exists in the Simple JWT Login WordPress plugin before version 3.6.8. The plugin fails to validate the audience of Google identity tokens, which could allow attackers to authenticate as any user whose email address is contained in a token. This issue affects sites with Google sign-in enabled. Further investigation is needed to determine the full scope of affected systems and to verify vendor remediation efforts.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-19714 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-19714
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-19714 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-19714
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/dc6e54eb-d856-484b-88c1-b3e04a37669d/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.