CVE-2025-12624: Improper Token Invalidation in WSO2 Identity Server Allows Access After Account Lock
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.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-12624?
CVE-2025-12624 has a high severity rating due to the risk of unauthorized access through unrevoked tokens.
How do I fix CVE-2025-12624?
To fix CVE-2025-12624, update to the latest version of WSO2 Identity Server where the token invalidation issue has been resolved.
What impact does CVE-2025-12624 have on user accounts?
CVE-2025-12624 allows ongoing access to user accounts even after they are locked, posing a significant security risk.
Which versions of WSO2 Identity Server are affected by CVE-2025-12624?
CVE-2025-12624 affects all versions of WSO2 Identity Server prior to the patch that implements token revocation on account lock.
Is there a workaround for CVE-2025-12624 while waiting for a patch?
Currently, there are no effective workarounds for CVE-2025-12624 other than applying the available security updates promptly.