Username Enumeration via Email OTP Flow in Multiple WSO2 Products Allows User Account Discovery

Summary

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.

Timeline

1. May 11, 2026, 8:45 AM UTCCVE published
2. May 11, 2026, 12:45 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. May 11, 2026, 12:46 PM UTCRecord last updated

Affected versions

• WSO2 WSO2 Identity Server

  From 5.10.0 · fixed in 5.10.0.379; From 5.11.0 · fixed in 5.11.0.426; From 5.11.0 · fixed in 5.11.0.431; From 6.0.0 · fixed in 6.0.0.253; From 6.1.0 · fixed in 6.1.0.254; From 7.0.0 · fixed in 7.0.0.131

• WSO2 WSO2 Open Banking IAM

  From 2.0.0 · fixed in 2.0.0.318

• WSO2 WSO2 Identity Server as Key Manager

  From 5.10.0 · fixed in 5.10.0.267

• org.wso2.carbon.identity.local.auth.emailotp:org.wso2.carbon.identity.local.auth.emailotp

  From 1.0.18 · fixed in 1.0.18.7

• org.wso2.carbon.extension.identity.authenticator.outbound.emailotp:org.wso2.carbon.identity.authenticator.emailotp

  From 4.1.0 · fixed in 4.1.0.8; From 4.1.4 · fixed in 4.1.4.9

• org.wso2.carbon.extension.identity.authenticator.outbound.emailotp:org.wso2.carbon.extension.identity.authenticator.emailotp.connector

  From 3.0.5 · fixed in 3.0.5.8; From 3.0.24 · fixed in 3.0.24.6; From 3.0.26 · fixed in 3.0.26.16

References 1