# CVE-2026-19714: Simple JWT Login < 3.6.8 - Unauthenticated Account Takeover via Missing Google id_token Audience Validation

> Unauthenticated attackers can take over any user account, including administrators, by exploiting missing Google id_token audience validation in the Simple JWT Login plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-vq3q-w9wv-xc6j

## What is CVE-2026-19714?

CVE-2026-19714 is a critical authentication bypass vulnerability in Unknown Simple JWT Login, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-19714?


## How do I fix CVE-2026-19714?

No fix has been published for CVE-2026-19714 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19714 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19714 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19714 and fix it if it is affected.

What it is: CVE-2026-19714 is a critical authentication bypass vulnerability in Unknown Simple JWT Login, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19714 exists.

Affected product: Unknown Simple JWT Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19714/ (Markdown: https://insights.sbomify.com/CVE-2026-19714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19714
- OSV: https://osv.dev/vulnerability/CVE-2026-19714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19714/
Summaries are generated and may contain mistakes; the official description above is the record.