Skip to content
Fencer Vulns
medium 4.8

CVE-2024-5617 json

Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks

published 2026-11-02 7 d ago modified 2026-11-09 3 h ago also EUVD-2024-55832

cvss
4.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account.

This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.

Patch / fix

  • WSO2 WSO2 API Manager 4.0.0.298, 4.2.0.95, 4.3.0.13
  • WSO2 WSO2 Identity Server 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33
  • WSO2 WSO2 Carbon Identity Management 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.92.84, 5.25.705.5, 7.0.78.19
  • WSO2 WSO2 Carbon User Manager Kernel 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7, 4.10.9.17

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6 d ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Carbon Identity Management
  • WSO2 WSO2 Carbon User Manager Kernel

Classification

Weakness
  • CWE-799 Improper Control of Interaction Frequency

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.