Security Advisory WSO2-2025-4727/CVE-2025-13173¶
Published: 2026-05-03
Version: 1.0.0
Severity: Medium
CVSS Score: 6.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L)
CVE IDs: CVE-2025-13173
AFFECTED PRODUCTS¶
- WSO2 API Control Plane: 4.6.0, 4.5.0
- WSO2 API Manager: 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0, 3.1.0
- WSO2 Identity Server as Key Manager: 5.10.0
- WSO2 Identity Server: 7.2.0, 7.1.0, 7.0.0, 6.1.0, 6.0.0, 5.11.0, 5.10.0
- WSO2 Open Banking AM: 2.0.0
- WSO2 Open Banking IAM: 2.0.0
- WSO2 Traffic Manager: 4.6.0, 4.5.0
- WSO2 Universal Gateway: 4.6.0, 4.5.0
OVERVIEW¶
Improper token revocation on session-bound token flow.
DESCRIPTION¶
Due to improper implementation of the session-bound token feature 1, tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This feature is disabled by default in WSO2 products. However, it can be enabled from the console by navigating to the application protocol configuration section, selecting the token binding type as “SSO Session”, and enabling the “Revoke token upon user logout” option.
IMPACT¶
This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.
SOLUTION¶
Community Users (Open Source)¶
Apply the relevant fixes to your product using the public fix(es) provided below.
- https://github.com/wso2/product-apim/pull/13967
- https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/3053
- https://github.com/wso2/carbon-identity-framework/pull/7757
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).
Support Subscription Holders¶
Update your product to the specified update level, or to a higher update level, to mitigate the identified vulnerability.
Info
WSO2 Support Subscription Holders may use WSO2 Updates in order to apply the fix.
| Product Name | Product Version | Update Level |
|---|---|---|
| WSO2 API Control Plane | 4.6.0 | 12 |
| WSO2 API Control Plane | 4.6.0 | 13 |
| WSO2 API Control Plane | 4.5.0 | 47 |
| WSO2 API Manager | 4.6.0 | 11 |
| WSO2 API Manager | 4.5.0 | 46 |
| WSO2 API Manager | 4.4.0 | 61 |
| WSO2 API Manager | 4.3.0 | 97 |
| WSO2 API Manager | 4.2.0 | 186 |
| WSO2 API Manager | 4.1.0 | 246 |
| WSO2 API Manager | 4.0.0 | 376 |
| WSO2 API Manager | 3.2.1 | 81 |
| WSO2 API Manager | 3.2.0 | 456 |
| WSO2 API Manager | 3.1.0 | 352 |
| WSO2 Identity Server | 7.2.0 | 3 |
| WSO2 Identity Server | 7.1.0 | 41 |
| WSO2 Identity Server | 7.0.0 | 133 |
| WSO2 Identity Server | 6.1.0 | 256 |
| WSO2 Identity Server | 6.0.0 | 255 |
| WSO2 Identity Server | 5.11.0 | 428 |
| WSO2 Identity Server | 5.10.0 | 381 |
| WSO2 Identity Server as Key Manager | 5.10.0 | 372 |
| WSO2 Open Banking AM | 2.0.0 | 401 |
| WSO2 Open Banking IAM | 2.0.0 | 421 |
| WSO2 Traffic Manager | 4.6.0 | 11 |
| WSO2 Traffic Manager | 4.5.0 | 45 |
| WSO2 Universal Gateway | 4.6.0 | 11 |
| WSO2 Universal Gateway | 4.5.0 | 46 |