CVE-2026-22706— Strapi: Password Reset Does Not Revoke Existing Refresh Sessions

Strapi: Password Reset Does Not Revoke Existing Refresh Sessions

Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30 days by default). Rotating credentials no longer terminated an active attacker session, defeating password reset as a containment measure. The patch in version 5.33.3 invalidates all refresh tokens associated with the user on every password change and password reset, regardless of whether a `deviceId` is supplied. A new device-scoped session is then issued to the caller as part of the response.

N/A

不充分的会话过期机制

Strapi 代码问题漏洞

Strapi是法国strapi社区的一套开源的内容管理系统（CMS）。 Strapi 5.33.3之前版本存在代码问题漏洞，该漏洞源于更改或重置用户密码时未默认使现有刷新令牌会话失效，可能导致先前获取刷新令牌的攻击者在合法用户重置密码后继续生成新的访问令牌，实现持久未授权访问。

N/A

N/A