JWT AUTH · CVE-2026-106466 · Package
NO FIX YET · SEE WHAT TO DO
The JWT Auth WordPress plugin keeps refresh tokens valid after a user changes their password or removes a connected device. An attacker holding an old refresh token can keep minting access tokens and stay logged in to the account, up to Administrator.
first public Nov 9, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
WordPress sites running the JWT Auth plugin through version 3.0.2 that issue refresh tokens for logins. Sites that do not use this plugin, or that run a version the sources do not list as affected, are not exposed. The sources do not say whether a managed WordPress host changes exposure.
Not affected if plugin-not-installed
Who cares jwt-auth, self-hosted, wordpress
wp plugin list or open Plugins in wp-admin and look for JWT Auth at 3.0.2 or lower3.0.2 as latest and the plugin as closed (Oct 23, 2026)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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.