Google JWT Token Audience Validation Missing in WordPress Plugin

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-19714 represents a critical authentication bypass in the Simple JWT Login WordPress plugin affecting versions before 3.6.8. The vulnerability stems from insufficient validation of Google identity tokens—specifically, the plugin fails to verify the 'audience' claim in JWT tokens. This allows attackers to craft or obtain valid Google tokens and use them to authenticate as any user on affected WordPress sites, including administrators, without possessing legitimate credentials. Every WordPress installation running this plugin with Google sign-in enabled is vulnerable to complete account takeover, making this a high-impact threat with CVSS 9.1 severity.

Casky's 283 matching skills leverage Claude's extended reasoning to detect the attack patterns mapped to TA0004 (Privilege Escalation) and TA0006 (Credential Access) within the MITRE ATT&CK framework. Practitioners using Casky would identify indicators including: JWT token manipulation attempts in authentication logs lacking proper audience validation, successful logins from unexpected Google OAuth sources with administrative privileges, and authentication requests bypassing normal credential verification chains. The platform's skills would surface anomalous patterns where standard email-based identity verification succeeds without corresponding legitimate OAuth flows, triggering alerts on privilege escalation where guest or low-privilege accounts suddenly gain admin access through JWT-based authentication mechanisms—the exact attack surface this vulnerability exposes.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-19714.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-19714

Casky has 283 skills that investigate the attack patterns behind CVE-2026-19714. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn