# CVE-2024-5617: WSO2 account lock bypass in multi-store authentication

Source: https://junglewise.ai/threats/cve-2024-5617-the-account-lock-feature-fails-to-correctly-enforce-account  
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-5617 · Severity: medium · CVSS 4.8 · Published 2026-11-02

WSO2 products that support multiple user stores fail to properly lock accounts when a user exists in both a primary and secondary store. An attacker can bypass account lockout protection by repeatedly attempting to log in with different passwords against the primary store account, potentially gaining unauthorized access to sensitive systems and data.

Technologies: [Wso2 Identity Server](https://junglewise.ai/threats/technologies/identity-server). Vendors: [Wso2](https://junglewise.ai/threats/vendors/wso2).

## Quick answers

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

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

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

**Is there a fix for CVE-2024-5617?** 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-5617 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2024-5617?** Check whether you run 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

A logic flaw in the account lock enforcement mechanism applies the lockout condition only to the secondary user store when identical usernames exist in both primary and secondary stores, leaving the primary store account unprotected. This enables brute force attacks via direct network authentication attempts. The vulnerability requires no special privileges or user interaction, as it affects the core authentication mechanism.

## Affected products

- WSO2 Identity Server

## Timeline

- 2026-11-02: disclosed

## References

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

## Related threats

- [WSO2 Identity Server privilege escalation via client credentials grant type](https://junglewise.ai/threats/cve-2025-11229-the-system-fails-to-properly-enforce-scope-authorization-when-the)
- [WSO2 Identity Server privilege escalation via shared database](https://junglewise.ai/threats/cve-2026-4052-this-issue-only-impacts-deployments-where-wso2-identity-server-is)
- [WSO2 Access token issuance without IDP status validation](https://junglewise.ai/threats/cve-2025-1397-when-utilizing-jwt-bearer-or-saml2-bearer-grant-types-the-system)
- [WSO2 products sensitive information disclosure in Event Publisher logs](https://junglewise.ai/threats/cve-2026-18800-when-an-event-publisher-output-adapter-is-configured-with)
- [WSO2 Identity Server content-type validation bypass](https://junglewise.ai/threats/cve-2025-13647-the-affected-component-fails-to-enforce-expected-validation)