JWT Auth <= 3.0.2 - Unauthenticated Persistent Unauthorized Account Access
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- JWT Auth – WordPress JSON Web Token Authentication
- Affected Version
<= 3.0.2- CVSS
- 5.3Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-106466
At a glance
CVE-2026-106466 is a medium-severity Improper Authentication vulnerability in the JWT Auth WordPress plugin, affecting versions <= 3.0.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2026, reported by Tarcísio Luchesi.
Vulnerability Overview
The JWT Auth – WordPress JSON Web Token Authentication plugin for WordPress is vulnerable to account persistence in all versions up to, and including, 3.0.2. This is due to the plugin not revoking the authentication token when a use changes or resets their password. This makes it possible for unauthenticated attackers to maintain session persistence. An attacker must have already obtained a valid refresh token for the target account before the password change, password reset, or device removal takes place.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in JWT Auth <= 3.0.2 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. No fixed build of this plugin is recorded for JWT Auth yet, so installs running <= 3.0.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in JWT Auth – WordPress JSON Web Token Authentication
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C