Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2024-9517

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

No exploitation reported by the sources we read.

  • Published2026-11-02
  • WeaknessCWE-613

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

dates in UTC
  1. 2026-11-0211:30CVE publishedCNA

Observed activity

isMalicious corpus · updated 2026-11-02 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-9517?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-9517?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Products declared by the CNA

As WSO2, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • WSO2 API Managerother versions: not affected
    Affected
    • ≥ 3.1.0, < 3.1.0.308fixed in 3.1.0.308custom
    • ≥ 3.2.0, < 3.2.0.429fixed in 3.2.0.429custom
    • ≥ 3.2.1, < 3.2.1.49fixed in 3.2.1.49custom
    • ≥ 4.0.0, < 4.0.0.315fixed in 4.0.0.315custom
    • ≥ 4.1.0, < 4.1.0.214fixed in 4.1.0.214custom
    • ≥ 4.2.0, < 4.2.0.149fixed in 4.2.0.149custom
    • ≥ 4.3.0, < 4.3.0.62fixed in 4.3.0.62custom
    • ≥ 4.4.0, < 4.4.0.25fixed in 4.4.0.25custom

    2 more version lines in the CVE record.

  • WSO2 Universal Gatewayother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.9fixed in 4.5.0.9custom
  • WSO2 Traffic Managerother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.9fixed in 4.5.0.9custom
  • WSO2 API Control Planeother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.10fixed in 4.5.0.10custom
  • WSO2 Identity Server as Key Managerother versions: not affected
    Affected
    • ≥ 5.10.0, < 5.10.0.324fixed in 5.10.0.324custom

    Not affected < 5.10.0 (status unknown)

  • WSO2 Identity Serverother versions: not affected
    Affected
    • ≥ 5.10.0, < 5.10.0.331fixed in 5.10.0.331custom
    • ≥ 5.11.0, < 5.11.0.376fixed in 5.11.0.376custom
    • ≥ 6.0.0, < 6.0.0.219fixed in 6.0.0.219custom
    • ≥ 6.1.0, < 6.1.0.205fixed in 6.1.0.205custom
    • ≥ 7.0.0, < 7.0.0.73fixed in 7.0.0.73custom

    Not affected < 5.10.0 (status unknown)

3 more products in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-02

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2024-9517 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE record2026-11-02
  • CNACVSS 3.14.92026-11-02
  • CNAweakness (CWE)CWE-6132026-11-02

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Published
2026-11-02

Frequently asked questions

What is CVE-2024-9517?

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.

Is CVE-2024-9517 actively exploited?

Active exploitation of CVE-2024-9517 has not been confirmed.

What is the CVSS score for CVE-2024-9517?

CVE-2024-9517 has a CVSS v3 base score of 4.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record