<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>JWT Auth WordPress Plugin (&lt;= 3.0.2) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/jwt-auth-wordpress-plugin--3.0.2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 09 Nov 2026 11:40:21 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/jwt-auth-wordpress-plugin--3.0.2/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>JWT Auth WordPress Plugin: Session persistence via non-revoked refresh tokens (CVE-2026-106466)</title><link>https://feed.craftedsignal.io/briefs/2026-11-jwt-auth-plugin-vulnerability/</link><pubDate>Mon, 09 Nov 2026 11:40:21 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-jwt-auth-plugin-vulnerability/</guid><description>The JWT Auth WordPress plugin (through 3.0.2) fails to invalidate refresh tokens after password resets or device removals, enabling attackers with stolen tokens to maintain persistent access.</description><content:encoded><![CDATA[<p>The JWT Auth WordPress plugin (versions 3.0.2 and earlier) contains a security flaw where refresh tokens are not invalidated when a user changes their password, resets their credentials, or removes a connected device. This vulnerability allows an attacker who has acquired a valid refresh token prior to these security events to continue generating new access tokens, bypassing the revocation of session access. The impact is significant as it potentially allows continued access up to the Administrator level.</p>
<h2 id="impact">Impact</h2>
<p>An attacker in possession of a refresh token can maintain persistent, unauthorized access to a compromised WordPress account despite the user performing password resets or security actions intended to clear active sessions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the JWT Auth plugin to a version beyond 3.0.2 as soon as a patch is released by the developer.</li>
<li>Implement monitoring for abnormal API access patterns or authentication spikes from existing tokens that should have been revoked after a credential change.</li>
<li>Force a global re-authentication or token rotation for all users if an account compromise is suspected, as local password resets may not be sufficient to terminate the attacker's session.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>wordpress</category><category>vulnerability</category><category>authentication-bypass</category></item></channel></rss>