Answer in brief
CVE-2024-7478 records a Medium severity (CVSS 5.8) vulnerability in Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carborn Identity Handler (generic), WSO2/WSO2 Identity Server (generic), WSO2/WSO2 Identity Server as Key Manager (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carborn Identity Handler (generic), WSO2/WSO2 Identity Server (generic), WSO2/WSO2 Identity Server as Key Manager (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.310 || >=3.2.0 <3.2.0.401 || >=3.2.1 <3.2.1.26 || >=4.0.0 <4.0.0.318 || >=4.1.0 <4.1.0.180 || >=4.2.0 <4.2.0.119 || >=4.3.0 <4.3.0.30 | 3.1.0.310, 3.2.0.401, 3.2.1.26, 4.0.0.318, 4.1.0.180, 4.2.0.119, 4.3.0.30 |
| WSO2/WSO2 Carborn Identity Handlergeneric | >=1.4.0 <1.4.0.15 || >=1.4.0 <1.4.0.16 || >=1.4.11 <1.4.11.14 || >=1.4.37 <1.4.37.1 || >=1.6.1 <1.6.1.5 || >=1.7.1 <1.7.1.1 || >=1.8.6 <1.8.6.5 || >=1.8.14 <1.8.14.1 || >=1.9.2 <1.9.2.4 | 1.4.0.15, 1.4.0.16, 1.4.11.14, 1.4.37.1, 1.6.1.5, 1.7.1.1, 1.8.6.5, 1.8.14.1, 1.9.2.4 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.326 || >=6.0.0 <6.0.0.214 || >=6.1.0 <6.1.0.198 || >=7.0.0 <7.0.0.67 | 5.10.0.326, 6.0.0.214, 6.1.0.198, 7.0.0.67 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.320 | 5.10.0.320 |
| WSO2/WSO2 Open Banking AMgeneric | >=2.0.0 <2.0.0.351 | 2.0.0.351 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.371 | 2.0.0.371 |
Published upstream
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.