Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-9517

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

Medium4.9EPSS 0.18%
Published
Updated
Reserved
Assigned by
WSO2

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 2 years later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-9517, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium4.9CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
NVDNVD · Awaiting Analysis3.1Medium4.9CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.9.

Weakness

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 3.1.0
    • affected 3.1.0 – < 3.1.0.308
    • affected 3.2.0 – < 3.2.0.429
    • affected 3.2.1 – < 3.2.1.49
    • affected 4.0.0 – < 4.0.0.315
    • affected 4.1.0 – < 4.1.0.214
    • affected 4.2.0 – < 4.2.0.149
    • affected 4.3.0 – < 4.3.0.62
    • affected 4.4.0 – < 4.4.0.25
    • affected 4.5.0 – < 4.5.0.9

  • WSO2 · WSO2 Universal Gateway

    • affected 4.5.0 – < 4.5.0.9

  • WSO2 · WSO2 Traffic Manager

    • affected 4.5.0 – < 4.5.0.9

  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.10

  • WSO2 · WSO2 Identity Server as Key Manager

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.324

  • WSO2 · WSO2 Identity Server

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.331
    • affected 5.11.0 – < 5.11.0.376
    • affected 6.0.0 – < 6.0.0.219
    • affected 6.1.0 – < 6.1.0.205
    • affected 7.0.0 – < 7.0.0.73

  • WSO2 · WSO2 Open Banking AM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.357

  • WSO2 · WSO2 Open Banking IAM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.377

  • WSO2 · WSO2 Carbon OAuth

    • affected 6.4.2 – < 6.4.2.148
    • affected 6.4.111 – < 6.4.111.122
    • affected 6.4.176 – < 6.4.176.26
    • affected 6.4.180 – < 6.4.180.10
    • affected 6.8.0 – < 6.8.0.44
    • affected 6.9.6 – < 6.9.6.21
    • affected 6.11.21 – < 6.11.21.64
    • affected 6.13.16 – < 6.13.16.13
    • affected 6.13.19 – < 6.13.19.7
    • affected 6.13.27 – < 6.13.27.1
    • affected 7.0.26 – < 7.0.26.37

What to do

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

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-9517 badge
[![CVE-2024-9517](https://trackcve.app/badge/CVE-2024-9517.svg)](https://trackcve.app/cve/CVE-2024-9517)

Record last updated .