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.
Published: 2026-08-06
Score: 4.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An authorization code that was issued to a user who has since been deleted is not being invalidated or removed when the user account is deleted. This flaw, classified as CWE‑613 (Improper Authorization), allows an attacker who obtains the orphaned authorization code along with the associated client credentials (client ID and client secret) to redeem the code for an access token on behalf of the now‑deleted user. The attacker could then access any resources or services that were originally granted to that user’s scopes, leading to unauthorized data exposure or service misuse.

Affected Systems

The vulnerability affects multiple WSO2 products, including WSO2 API Control Plane, WSO2 API Manager, WSO2 Carbon OAuth, WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 Open Banking AM, WSO2 Open Banking IAM, WSO2 Traffic Manager, and WSO2 Universal Gateway. No specific version range is provided in the available data.

Risk and Exploitability

The CVSS score of 4.9 indicates a moderate risk level. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. Based on the description, the attack requires both a valid but orphaned authorization code and the corresponding client credentials, which may be obtained if an attacker has previously compromised the system or obtained credentials through social engineering. Because an attacker does not need to perform a complex exploit but must possess these two artifacts, the likelihood of exploitation remains moderate, especially in environments where credentials are not frequently rotated or revoked.

Generated by OpenCVE AI on August 6, 2026 at 09:26 UTC.

Remediation

Vendor Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-2753/#solution


OpenCVE Recommended Actions

  • Follow WSO2’s official instructions to apply the patch for the affected products as described at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-2753/#solution
  • Rotate or revoke any client credentials that belong to deleted users to prevent the reuse of their authorization codes
  • Manually delete or invalidate remaining authorization codes associated with deleted users from the system to ensure no orphaned codes persist

Generated by OpenCVE AI on August 6, 2026 at 09:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 06 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 06 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
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.
Title Authorization Code issued for Deleted User reuse in Multiple WSO2 Products Allows Unauthorized Access
First Time appeared Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Oauth
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
Weaknesses CWE-613
CPEs cpe:2.3:a:wso2:wso2_api_control_plane:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server_as_key_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_am:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_iam:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_traffic_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_universal_gateway:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Oauth
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

Wso2 Wso2 Api Control Plane Wso2 Api Manager Wso2 Carbon Oauth Wso2 Identity Server Wso2 Identity Server As Key Manager Wso2 Open Banking Am Wso2 Open Banking Iam Wso2 Traffic Manager Wso2 Universal Gateway
cve-icon MITRE

Status: PUBLISHED

Assigner: WSO2

Published:

Updated: 2026-08-06T12:34:10.613Z

Reserved: 2024-09-19T08:21:20.017Z

Link: CVE-2024-8995

cve-icon Vulnrichment

Updated: 2026-08-06T12:34:07.027Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T09:30:02Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration