Post-lock resource access via unrevoked tokens
Published Apr 16, 2026 · Updated Apr 16, 2026
Improper token invalidation in WSO2 Identity Server 5.2.0 before 5.2.0.35 allows remote authenticated users to retain resource access. The account-locking path leaves previously issued, unexpired access tokens valid instead of revoking or invalidating them. Exploitation requires a token issued before the account is locked and preserves only that token's existing authorization until expiration.
Summary
What happened
Improper token invalidation in WSO2 Identity Server 5.2.0 before 5.2.0.35 allows remote authenticated users to retain resource access. The account-locking path leaves previously issued, unexpired access tokens valid instead of revoking or invalidating them. Exploitation requires a token issued before the account is locked and preserves only that token's existing authorization until expiration.
The record
- CVE
- CVE-2025-12624
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- WSO2
- Product
- WSO2 Identity Server
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2.0 <5.2.0.35
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo