CVE-2024-7478 — Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Identity Server, WSO2 Identity Server As Key Manager…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Manager | ≥ 3.2.0 and < 3.2.0.401≥ 3.2.1 and < 3.2.1.26≥ 4.0.0 and < 4.0.0.318≥ 4.1.0 and < 4.1.0.180≥ 4.2.0 and < 4.2.0.119≥ 4.3.0 and < 4.3.0.30≥ 3.1.0 and < 3.1.0.310 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Identity Server | ≥ 5.10.0 and < 5.10.0.326≥ 6.0.0 and < 6.0.0.214≥ 6.1.0 and < 6.1.0.198≥ 7.0.0 and < 7.0.0.67 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Identity Server As Key Manager | ≥ 5.10.0 and < 5.10.0.320 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Open Banking Am | ≥ 2.0.0 and < 2.0.0.351 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Open Banking Iam | ≥ 2.0.0 and < 2.0.0.371 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carborn Identity Handler |
≥ 1.4.0 and < 1.4.0.15≥ 1.4.0 and < 1.4.0.16≥ 1.4.11 and < 1.4.11.14≥ 1.4.37 and < 1.4.37.1≥ 1.6.1 and < 1.6.1.5≥ 1.7.1 and < 1.7.1.1≥ 1.8.6 and < 1.8.6.5≥ 1.8.14 and < 1.8.14.1 and 1 more≥ 1.9.2 and < 1.9.2.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.8 | CVSS 3.1 | Medium | 3.9 | 1.4 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
| 5.8 | CVSS 3.1 | Medium | — | — | WSO2 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Source status changed · Published → Received
- Record published
- CVSS changed · 5.8
- Source status changed · → Published
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2025-0326 Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access 1d
- Medium CVE-2024-6423 Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage 1d
- Medium CVE-2024-5563 Incomplete reCaptcha Implementation in Authentication Flows in WSO2 Identity Server Allows Brute Force Attacks 1d
- Medium CVE-2024-5139 Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Enables UI Manipulation and Redirection 1d
- Medium CVE-2024-4989 Open Redirection via Callback URL in WSO2 API Manager Allows Phishing Attacks 1d
- Medium CVE-2024-2323 Password Brute Force via Password History Validation in Multiple WSO2 Products Allows User Account Discovery 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-7478 is "Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery", rated Medium. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.8 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.