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