CVE-2024-8995 Details
Description
Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials (client ID and client secret), they can leverage these unused codes to obtain access tokens on behalf of users who have already been deleted. This may lead to unauthorized access to sensitive resources and services, contingent on the scopes originally authorized for the compromised authorization code.
A vulnerability exists in multiple WSO2 products, including API Manager, Identity Server, Traffic Manager, and others, where unused authorization codes issued to deleted users are not properly invalidated or removed. This oversight allows these codes to persist and potentially be reused. If an attacker has both the authorization code and the corresponding client credentials (client ID and client secret), they can use these codes to obtain access tokens on behalf of deleted users. This could result in unauthorized access to sensitive resources and services, depending on the scopes originally associated with the compromised authorization code.
WSO2 community users can apply the public fix available on GitHub. Support subscription holders should update to the specified update level for their product version. Details on the update levels for different WSO2 products are available in the WSO2 security advisory.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 6, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-2753/ | WSO2 LLC | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-613 | Insufficient Session Expiration | WSO2 LLC |
Affected Products
| Product | Versions |
|---|---|
| wso2 api control plane | >= 4.5.0, < 4.5.0.56 >= 4.6.0, < 4.6.0.20 |
CPE
Remediation
| |
| wso2 api manager | >= 3.1.0, < 3.1.0.320 >= 3.2.0, < 3.2.0.413 >= 3.2.1, < 3.2.1.90 >= 4.0.0, < 4.0.0.334 >= 4.1.0, < 4.1.0.255 >= 4.2.0, < 4.2.0.195 >= 4.3.0, < 4.3.0.106 >= 4.4.0, < 4.4.0.70 >= 4.5.0, < 4.5.0.55 >= 4.6.0, < 4.6.0.19 |
CPE
Remediation
| |
| wso2 identity server | >= 5.10.0, < 5.10.0.338 >= 5.11.0, < 5.11.0.395 >= 6.0.0, < 6.0.0.229 >= 6.1.0, < 6.1.0.208 |
CPE
Remediation
| |
| wso2 identity server as key manager | >= 5.10.0, < 5.10.0.338 |
CPE
Remediation
| |
| wso2 open banking am | >= 2.0.0, < 2.0.0.369 |
CPE
Remediation
| |
| wso2 open banking iam | >= 2.0.0, < 2.0.0.389 |
CPE
Remediation
| |
| wso2 traffic manager | >= 4.5.0, < 4.5.0.54 >= 4.6.0, < 4.6.0.19 |
CPE
Remediation
| |
| wso2 universal gateway | >= 4.5.0, < 4.5.0.55 >= 4.6.0, < 4.6.0.19 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 27, 2026 | CVE Translated | [email protected] |
| Aug 13, 2026 | Reanalysis | [email protected] |
| Aug 10, 2026 | Initial Analysis | [email protected] |
| Aug 6, 2026 | CVE Modified | CISA-ADP |
| Aug 6, 2026 | New CVE Received | WSO2 LLC |