# CVE-2024-9517: WSO2 refresh token grant account lockout bypass

Source: https://junglewise.ai/threats/cve-2024-9517-the-refresh-token-grant-type-in-wso2-products-fails-to-re-validate  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2024-9517 · Severity: medium · CVSS 4.9 · Published 2026-11-02

WSO2's identity and access management products issue new access tokens via refresh token grants without re-validating whether user accounts have been locked or blocked. An attacker who obtains a refresh token can bypass account lockout mechanisms to gain ongoing access to a blocked user's account and associated resources, potentially leading to unauthorized data access or fraudulent actions.

Technologies: [WSO2 API Manager](https://junglewise.ai/threats/technologies/api-manager), [WSO2 Identity Server](https://junglewise.ai/threats/technologies/identity-server). Vendors: [Wso2](https://junglewise.ai/threats/vendors/wso2).

## Quick answers

**Is CVE-2024-9517 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-9517 being exploited in the wild.

**How severe is CVE-2024-9517?** Medium severity, with a CVSS score of 4.9, published 2 November 2026.

**Which products and versions are affected?** WSO2 WSO2 API Manager; WSO2 WSO2 Identity Server.

**Is there a fix for CVE-2024-9517?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2024-9517 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2024-9517?** Check whether you run WSO2 API Manager or WSO2 Identity Server. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The refresh token grant type in WSO2 products fails to re-validate account status (blocked, locked, or disabled) when issuing new access tokens. An attacker in possession of a valid refresh token can obtain new access tokens for accounts that have since been locked or blocked in the user store, circumventing account lockout controls. This is a server-side validation weakness exploitable by any party holding a refresh token from a later-blocked account.

## Affected products

- WSO2 WSO2 API Manager
- WSO2 WSO2 Identity Server

## Timeline

- 2026-11-02: disclosed

## References

- [https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3676/](https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3676/)

## Related threats

- [WSO2 RemoteUserStoreManagerService insufficient password change validation](https://junglewise.ai/threats/cve-2024-2323-the-remoteuserstoremanagerservice-does-not-sufficiently-validate)