CVE-2024-5617
Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks
Description
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.
INFO
Published Date :
Nov. 2, 2026, 6:17 a.m.
Last Modified :
Nov. 2, 2026, 6:17 a.m.
Remotely Exploit :
Yes !
Source :
ed10eef1-636d-4fbe-9993-6890dfa878f8
Affected Products
The following products are affected by CVE-2024-5617
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | ed10eef1-636d-4fbe-9993-6890dfa878f8 |
Solution
- Ensure account lockout logic targets the correct user store.
- Implement robust authentication checks across all user stores.
- Test lockout functionality with duplicate usernames in multiple stores.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-5617.
| URL | Resource |
|---|---|
| https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-5617 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-5617
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-5617 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-5617 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by ed10eef1-636d-4fbe-9993-6890dfa878f8
Nov. 02, 2026
Action Type Old Value New Value Added Description 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. Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Added CWE CWE-799 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2024/5xxx/CVE-2024-5617.json">CVE-2024-5617</a> Added Reference https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/