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.
Published: 2026-11-09
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: Persistent unauthorized access via refresh token misuse
Action: Immediate Patch
AI Analysis

Impact

The vulnerability lies in the JWT Auth WordPress plugin, where previously issued refresh tokens are not invalidated when a user changes or resets their password or disconnects a device. Because of this, an attacker in possession of a valid refresh token before such a password or device reset can continue to obtain new access tokens indefinitely, maintaining authenticated access to the account, potentially at the Administrator level. This flaw allows an attacker to bypass authentication controls and persistently retain elevated privileges.

Affected Systems

WordPress sites running the JWT Auth plugin with a version up to and including 3.0.2 are impacted. Admins who do not update the plugin are at risk. The vulnerability is specific to that plugin rather than the WordPress core.

Risk and Exploitability

The CVSS score of 7.5 reflects a high impact, though the EPSS score is not available, so the exact exploitation probability is uncertain. The flaw can be abused by anyone who can grab a refresh token prior to a password change—through credential theft, social engineering, or compromised devices. Once in possession of that token, the attacker can repeatedly request new access tokens, evading authentication checks and continuing to act as the account holder. Based on the description, it is inferred that the attack can be carried out remotely via the plugin’s API endpoints, meaning that network presence is sufficient for exploitation. The vulnerability is not present in CISA’s KEV catalog, but its high severity warrants immediate action.

Generated by OpenCVE AI on November 9, 2026 at 15:55 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the JWT Auth plugin to version 3.0.3 or later, which corrects the refresh token revocation logic.
  • Revoke all existing refresh tokens for all users, for example, by forcing a global logout or resetting the JWT secret, to eliminate previously issued tokens.
  • Audit user accounts for unexpected or suspicious tokens and monitor access logs for unauthorized token usage.

Generated by OpenCVE AI on November 9, 2026 at 15:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 09 Nov 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-613

Mon, 09 Nov 2026 10:30:00 +0000

Type Values Removed Values Added
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.
Title JWT Auth <= 3.0.2 - Unauthenticated Account Access Persistence via Insufficient Refresh Token Revocation
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-11-09T13:51:55.405Z

Reserved: 2026-10-06T17:28:54.820Z

Link: CVE-2026-106466

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-09T11:17:19.940

Modified: 2026-11-09T14:17:05.943

Link: CVE-2026-106466

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-09T16:00:20Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration