CVE-2024-9517

Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts

Published Nov 2, 2026 CVSS 3.1 · 4.9 Medium EPSS < 1% KEV · Not listed
Description
The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing account lockout mechanisms.

This vulnerability can lead to unauthorized access to user accounts and their associated resources. Attackers can leverage this to perform actions on behalf of blocked users, potentially leading to privilege escalation or data exfiltration depending on the permissions of the compromised account.

Analysis

AI-generated

Technical impact

The refresh token grant type in several WSO2 products fails to re‑validate an account’s status before issuing new access tokens. Because blocked accounts are still granted tokens, an attacker can obtain valid credentials even after an account has been disabled, leading to unauthorized actions in place of the blocked user. This flaw may enable privilege escalation or data exfiltration depending on the permissions of the compromised account.

Affected Systems

The vulnerability affects WSO2 API Control Plane, API Manager, Carbon OAuth, Identity Server, Identity Server as Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager, and Universal Gateway. No specific version information is supplied, so all releases are potentially impacted until a patch is applied.

Risk and Exploitability

With a CVSS score of 4.9 the vulnerability is considered moderate, and the EPSS score is unavailable, suggesting limited but non‑negligible exploitation probability. The flaw is not listed in the CISA KEV catalog. Attackers can exploit the weakness by sending a refresh token request through the OAuth flow; any holder of a valid refresh token for a blocked account can obtain a new access token, bypassing lockout controls.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Apply the WSO2 security advisory WSO2‑2024‑3676 patch or upgrade to a fixed release as instructed at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3676/#solution
  • Revoke all existing refresh tokens for affected accounts and force users to re‑authenticate after account status changes
  • Ensure that the account status is re‑validated during each refresh token issuance to prevent blocked accounts from receiving new tokens

Generated by OpenCVE AI on November 2, 2026 at 12:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Wso2 api Control Plane
Wso2 api Manager
Wso2 identity Server
Vendors & Products Wso2 api Control Plane
Wso2 api Manager
Wso2 identity Server
Type Values Removed Values Added
Description The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing account lockout mechanisms. This vulnerability can lead to unauthorized access to user accounts and their associated resources. Attackers can leverage this to perform actions on behalf of blocked users, potentially leading to privilege escalation or data exfiltration depending on the permissions of the compromised account.
Title Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts
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'}