Skip to content
Fencer Vulns
medium 5.3

CVE-2024-0391 json

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

published 2026-05-11 5 mo ago modified 2026-11-08 18 h ago also EUVD-2024-16187

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

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.

Patch / fix

  • WSO2 WSO2 Identity Server 5.10.0.379, 5.11.0.426, 5.11.0.431, 6.0.0.253, 6.1.0.254, 7.0.0.131
  • WSO2 WSO2 Open Banking IAM 2.0.0.318
  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.267
  • WSO2 Email OTP Authenticator 1.0.18.7, 1.0.24
  • WSO2 WSO2 Carbon Authenticator Library For EmailOTP 3.0.5.8, 3.0.24.6, 3.0.26.16, 4.1.0.8, 4.1.4.9, 4.1.22

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5 mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected products

  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Open Banking IAM
  • WSO2 WSO2 Identity Server as Key Manager
  • WSO2 Email OTP Authenticator
  • WSO2 WSO2 Carbon Authenticator Library For EmailOTP

Classification

Weakness
  • CWE-204 Observable Response Discrepancy

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.