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.
Problem types
CWE-204 Observable response discrepancy
Product status
Any version before 5.10.0
5.10.0 (custom) before 5.10.0.379
5.11.0 (custom) before 5.11.0.426
5.11.0 (custom) before 5.11.0.431
6.0.0 (custom) before 6.0.0.253
6.1.0 (custom) before 6.1.0.254
7.0.0 (custom) before 7.0.0.131
Any version before 2.0.0
2.0.0 (custom) before 2.0.0.318
Any version before 5.10.0
5.10.0 (custom) before 5.10.0.267
1.0.18 (custom) before 1.0.18.7
1.0.24 (custom)
4.1.0 (custom) before 4.1.0.8
4.1.4 (custom) before 4.1.4.9
4.1.22 (custom)
3.0.5 (custom) before 3.0.5.8
3.0.24 (custom) before 3.0.24.6
3.0.26 (custom) before 3.0.26.16
References
security.docs.wso2.com/...ty-advisories/2026/WSO2-2024-3115/