Technical impact
The flaw causes the account lockout logic to be applied only to the secondary user store when the same username exists in both primary and secondary stores, leaving the primary account open to repeated authentication attempts. This weakness, documented as CWE-799, allows an attacker who knows or guesses a username to bypass the intended lockout mechanism and try multiple passwords, potentially gaining unauthorized access to protected resources.
Affected Systems
The vulnerability affects all versions of WSO2 API Manager, WSO2 Carbon Identity Management, WSO2 Carbon User Manager Kernel and WSO2 Identity Server that have not applied the latest update. No specific product versions are listed, so any deployment of these products that remains uncompromised is considered at risk.
Risk and Exploitability
The CVSS score of 4.8 reflects a moderate severity; the EPSS score is unavailable and the issue is not listed in CISA KEV, indicating no confirmed widespread exploitation yet. However, the design flaw permits a straightforward brute‑force attack by repeatedly attempting login credentials against the primary user store, a scenario that is possible via any exposed authentication endpoint. Attackers only need valid user identifiers to exploit this bypass, making the vulnerability potentially impactful if adequate account lockout rates are not enforced elsewhere. Based on the description, the likely attack vector is any exposed authentication endpoint.