Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.0
WSO2 Identity Server: Locked Users Can Keep Access to Protected Resources
CVE-2025-12624
Summary
A locked user account in WSO2 Identity Server can still access protected resources using previously issued access tokens. This means that a locked account can continue to access sensitive data or perform actions, even though the account is supposed to be restricted. You should update your WSO2 Identity Server configuration to ensure that access tokens are properly revoked when a user account is locked.
Original title
Active access tokens are not revoked or invalidated when a user account is locked within WSO2 Identity Server. This failure to enforce revocation allows previously issued, valid tokens to remain us...
Original description
Active access tokens are not revoked or invalidated when a user account is locked within WSO2 Identity Server. This failure to enforce revocation allows previously issued, valid tokens to remain usable, enabling continued access to protected resources by locked user accounts.
The security consequence is that a locked user account can maintain access to protected resources through the use of existing, unexpired access tokens. This creates a security gap where access control policies are bypassed, potentially leading to unauthorized data access or actions until the tokens naturally expire.
The security consequence is that a locked user account can maintain access to protected resources through the use of existing, unexpired access tokens. This creates a security gap where access control policies are bypassed, potentially leading to unauthorized data access or actions until the tokens naturally expire.
nvd CVSS3.1
6.0
Vulnerability type
CWE-613
Published: 16 Apr 2026 · Updated: 17 Apr 2026 · First seen: 16 Apr 2026