JWT Auth <= 3.0.2 — Unauthenticated Persistent Unauthorized Account Access
CVE-2026-106466Published · Updated Action summary
Affected: ≤3.0.2No patch available
What to do until a fix ships- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
JWT Auth – WordPress JSON Web Token Authentication jwt-auth
- Affected≤ 3.0.2
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 3.0.2. No fixed version has been released.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under JWT Auth – WordPress JSON Web Token Authentication.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- 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.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch JWT Auth – WordPress JSON Web Token Authentication to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Tarcísio Luchesi.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in JWT Auth – WordPress JSON Web Token Authentication
All 2| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Critical9.1 | Algorithm Confusion ≤2.1.0Update to 2.1.1 | CVE-2021-46743 |
- Critical9.1Algorithm Confusion
≤2.1.0Update to 2.1.1
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.