CVE-2025-12624: Improper Token Invalidation in WSO2 Identity Server Allows Access After Account Lock

Published Apr 16, 2026
·
Updated

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

2 affected components
WSO2 WSO2 Identity Server
WSO2 Identity Server=5.2.0

Remediation

Information

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4684/#solution

Event History

Apr 16, 2026
CVE Published
via MITRE·10:25 AM
Data Sourced
via MITRE·10:25 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203