CVE-2024-0391
Description
The check user account lock states feature within the email OTP flow fails to validate user input, allowing an attacker to infer the existence of registered user accounts.
The discovery of valid usernames can increase the risk of brute-force and social engineering attacks. Attackers can leverage this information to craft targeted phishing campaigns or other malicious activities aimed at tricking users into divulging sensitive data, potentially damaging the organization's reputation and leading to regulatory non-compliance and financial consequences.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The email OTP flow in WSO2 Identity Server products fails to validate user input when checking account lock states, enabling username enumeration.
The vulnerability resides in the check user account lock states feature within the email OTP flow of WSO2 Identity Server, Identity Server as Key Manager, and Open Banking IAM. Due to the absence of input validation, a remote attacker can determine whether a given username corresponds to a registered account by observing the response from this feature [1].
An attacker can exploit this without authentication by sending crafted requests to the email OTP endpoint. The feature does not properly validate the user input, allowing the attacker to infer the existence of valid usernames based on the system's response. No special network position is required beyond standard internet access [1].
Successful exploitation yields a list of valid usernames, which significantly increases the risk of brute-force attacks and targeted social engineering campaigns. Attackers can use this information to craft phishing emails or other malicious activities aimed at tricking users into divulging sensitive data. This can lead to reputational damage, loss of customer trust, regulatory non-compliance, and financial consequences [1].
WSO2 has addressed this issue by releasing fixes for the affected product versions. Users are advised to apply the relevant fix from the provided GitHub pull request or upgrade to the latest unaffected version of the respective product. For support subscription holders, updating to the specified update levels will mitigate the vulnerability [1].
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
1News mentions
0No linked articles in our index yet.