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.
Metrics
Affected Vendors & Products
References
History
Thu, 16 Apr 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 16 Apr 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wso2 identity Server
|
|
| Vendors & Products |
Wso2 identity Server
|
Thu, 16 Apr 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Improper Token Invalidation in WSO2 Identity Server Allows Access After Account Lock | |
| First Time appeared |
Wso2
Wso2 wso2 Identity Server |
|
| Weaknesses | CWE-613 | |
| CPEs | cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Wso2
Wso2 wso2 Identity Server |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: WSO2
Published: 2026-04-16T10:25:19.789Z
Updated: 2026-04-16T12:30:14.886Z
Reserved: 2025-11-03T06:20:27.950Z
Link: CVE-2025-12624
Updated: 2026-04-16T12:19:52.974Z
Status : Received
Published: 2026-04-16T11:16:26.447
Modified: 2026-04-16T11:16:26.447
Link: CVE-2025-12624
No data.