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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 4.9, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 8 products from wso2, from wso2, from wso2 and 5 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-08-06T08:16:27.687
2026-08-13T13:18:42.173
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 4.9 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wso2 | api_control_plane | < 4.5.0.56 | Yes |
| Application | wso2 | api_control_plane | < 4.6.0.20 | Yes |
| Application | wso2 | api_manager | < 3.1.0.320 | Yes |
| Application | wso2 | api_manager | < 3.2.0.413 | Yes |
| Application | wso2 | api_manager | < 3.2.1.90 | Yes |
| Application | wso2 | api_manager | < 4.0.0.334 | Yes |
| Application | wso2 | api_manager | < 4.1.0.255 | Yes |
| Application | wso2 | api_manager | < 4.2.0.195 | Yes |
| Application | wso2 | api_manager | < 4.3.0.106 | Yes |
| Application | wso2 | api_manager | < 4.4.0.70 | Yes |
| Application | wso2 | api_manager | < 4.5.0.55 | Yes |
| Application | wso2 | api_manager | < 4.6.0.19 | Yes |
| Application | wso2 | identity_server | < 5.10.0.338 | Yes |
| Application | wso2 | identity_server | < 5.11.0.395 | Yes |
| Application | wso2 | identity_server | < 6.0.0.229 | Yes |
| Application | wso2 | identity_server | < 6.1.0.208 | Yes |
| Application | wso2 | identity_server_as_key_manager | < 5.10.0.338 | Yes |
| Application | wso2 | open_banking_am | < 2.0.0.369 | Yes |
| Application | wso2 | open_banking_iam | < 2.0.0.389 | Yes |
| Application | wso2 | traffic_manager | < 4.5.0.54 | Yes |
| Application | wso2 | traffic_manager | < 4.6.0.19 | Yes |
| Application | wso2 | universal_gateway | < 4.5.0.55 | Yes |
| Application | wso2 | universal_gateway | < 4.6.0.19 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For wso2's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.