Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.5
CVE-2026-106466: JWT Auth plugin retains stolen token after password reset
CVE-2026-106466 · published 9 days ago
Summary
The WordPress JWT Auth plugin does not cancel old refresh tokens when a user changes their password or removes a device. This means anyone who already has a refresh token can continue to generate new login tokens and stay signed in, even after the password is changed. Update the plugin to the latest version or manually revoke existing refresh tokens to remove the risk.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| unknown | jwt auth | <= 3.0.2 |
Original advisory text
JWT Auth <= 3.0.2 - Unauthenticated Account Access Persistence via Insufficient Refresh Token Revocation
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.
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Type
CWE-613Insufficient Session Expiration
Timeline
Published9 Nov 2026
Updated19 Nov 2026
First seen9 Nov 2026
Track software like this
Free during beta