---
id: CVE-2025-12624
title: >-
  Active access tokens are not revoked or invalidated when a user account is
  locked within WSO2 Identity Server
summary: >-
  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
  prote…
severity: medium
cvss: 6
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L'
cwe:
  - CWE-613
vendor: wso2
product: identity_server
affected:
  - identity_server = 5.2.0
published: '2026-04-16'
updated: '2026-09-30'
sourceUpdated: '2026-09-30T22:10:00.273'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-12624'
references:
  - url: >-
      https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4684/
    label: ed10eef1-636d-4fbe-9993-6890dfa878f8
tags:
  - nvd
epss: 0.00177
epssPercentile: 0.06583
ingestedAt: '2026-09-30T22:27:27.758Z'
---

## Overview

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

- `identity_server = 5.2.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.