<?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/"><channel><title>Session-Reuse — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/session-reuse/</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>Tue, 12 May 2026 22:25:05 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/session-reuse/feed.xml" rel="self" type="application/rss+xml"/><item><title>SillyTavern Session Reuse After Password Change</title><link>https://feed.craftedsignal.io/briefs/2026-05-sillytavern-session-reuse/</link><pubDate>Tue, 12 May 2026 22:25:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-sillytavern-session-reuse/</guid><description>SillyTavern versions 1.17.0 and earlier do not invalidate existing sessions after a password change, allowing attackers with stolen session cookies to retain access, even after the victim resets their password, and nullifies the password reset as a recovery measure against session theft.</description><content:encoded><![CDATA[<p>SillyTavern, a popular open-source AI chatbot interface, is vulnerable to session reuse. Prior to version 1.18.0, changing a user&rsquo;s password does not invalidate existing session cookies. This vulnerability stems from the application&rsquo;s reliance on cookie-session for authentication, where session data is stored client-side. An attacker who has obtained a valid session cookie can maintain persistent access to a user&rsquo;s account, even after the user changes their password. The default cookie lifespan of 400 days gives attackers a very long window for potential exploitation. Defenders should ensure that their SillyTavern installations are upgraded to version 1.18.0 or later to mitigate this risk.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a user&rsquo;s valid session cookie through methods like XSS, man-in-the-middle attacks, or physical access to the user&rsquo;s device.</li>
<li>The attacker imports the stolen cookie into their browser.</li>
<li>The attacker authenticates to the SillyTavern application using the imported cookie.</li>
<li>The victim, suspecting account compromise, changes their password via the <code>/api/users/change-password</code> endpoint or <code>/api/users/recover-step2</code> after initiating an account recovery.</li>
<li>The SillyTavern application updates the password hash in the database but does not invalidate the existing session cookie.</li>
<li>The attacker, still possessing the valid cookie, continues to access the victim&rsquo;s account and perform privileged actions.</li>
<li>The attacker views sensitive information, modifies user settings, or interacts with the AI chatbot as the compromised user.</li>
<li>The attacker maintains unauthorized access until the cookie expires, by default after 400 days.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers who have stolen session cookies to maintain persistent control over user accounts. Even after a password reset, attackers can continue accessing sensitive information, impersonate the user, and perform unauthorized actions. With a default cookie lifespan of 400 days, this vulnerability presents a significant risk of long-term account compromise, especially in environments where users may be slow to update their passwords or revoke sessions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade SillyTavern installations to version 1.18.0 or later to address the session invalidation vulnerability.</li>
<li>Enable web server logging and deploy the &ldquo;Detect SillyTavern Session Cookie Use After Password Change&rdquo; Sigma rule to identify suspicious activity associated with session reuse.</li>
<li>Implement strict cookie security policies, including setting the <code>HttpOnly</code> and <code>Secure</code> flags, to reduce the risk of session cookie theft.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>credential-access</category><category>session-reuse</category><category>web-application</category></item></channel></rss>