CVE-2025-12624 | WSO2 Identity Server up to 5.2.0.34 Access Token session expiration

VDB-357914 · CVE-2025-12624 · GCVE-0-2025-12624 WSO2 IDENTITY SERVER UP TO 5.2.0.34 ACCESS TOKEN SESSION EXPIRATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.4 $0-$5k 1.32+ Summaryinfo A vulnerability was found in WSO2 Identity Server up to 5.2.0.34 and classified as problematic. The impacted element is an unknown function of the component Access Token Handler. Such manipulation leads to session expiration. This vulnerability is traded as CVE-2025-12624. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in WSO2 Identity Server up to 5.2.0.34. Affected by this issue is an unknown code of the component Access Token Handler. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. CVE summarizes: 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. The advisory is available at security.docs.wso2.com. This vulnerability is handled as CVE-2025-12624 since 11/03/2025. The exploitation is known to be difficult. The attack may be launched remotely. The technical details are unknown and an exploit is not available. Upgrading to version 5.2.0.35 eliminates this vulnerability. Productinfo Vendor WSO2 Name Identity Server Version 5.2.0.0 5.2.0.1 5.2.0.2 5.2.0.3 5.2.0.4 5.2.0.5 5.2.0.6 5.2.0.7 5.2.0.8 5.2.0.9 5.2.0.10 5.2.0.11 5.2.0.12 5.2.0.13 5.2.0.14 5.2.0.15 5.2.0.16 5.2.0.17 5.2.0.18 5.2.0.19 5.2.0.20 5.2.0.21 5.2.0.22 5.2.0.23 5.2.0.24 5.2.0.25 5.2.0.26 5.2.0.27 5.2.0.28 5.2.0.29 5.2.0.30 5.2.0.31 5.2.0.32 5.2.0.33 5.2.0.34 License commercial CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.5 VulDB Meta Temp Score: 5.4 VulDB Base Score: 5.0 VulDB Temp Score: 4.8 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.0 CNA Vector (WSO2): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Session expiration CWE: CWE-613 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Identity Server 5.2.0.35 Timelineinfo 11/03/2025 CVE reserved 04/16/2026 +163 days Advisory disclosed 04/16/2026 +0 days VulDB entry created 04/16/2026 +0 days VulDB entry last update Sourcesinfo Advisory: security.docs.wso2.com Status: Confirmed CVE: CVE-2025-12624 (🔒) GCVE (CVE): GCVE-0-2025-12624 GCVE (VulDB): GCVE-100-357914 Entryinfo Created: 04/16/2026 13:31 Changes: 04/16/2026 13:31 (63) Complete: 🔍 Cache ID: 99:CCB:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸