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

Medium 6.0 Published Updated

Attackers with locked accounts can retain access to protected resources using unrevoked access tokens, bypassing account lockout security controls.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-12624?

CVE-2025-12624 is a medium-severity authentication bypass vulnerability in Wso2 Identity Server, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-613

Which versions are affected by CVE-2025-12624?

It affects 1 product.

Products include Wso2 Identity Server.

How do I fix CVE-2025-12624?

No fix has been published for CVE-2025-12624 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2025-12624 being exploited?

There is no known exploitation of CVE-2025-12624 in the wild and no public exploit code.

All Wso2 Identity Server vulnerabilities

Sources

Also known as GHSA-gw5f-5fmc-2xp2.

Is CVE-2025-12624 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free