CVE-2024-7478

Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery

  • Medium 5.8

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.

Key facts

Published
21 Oct 2026
Last changed
30 Oct 2026
Assigned by
WSO2
EPSS
0.235% likely to be exploited in the next 30 days, higher than 14.585% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.8CVSS 3.1, Mediumfrom the CNA (WSO2)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

What to do

  • Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3606/#solutionCNA solution statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-24 CAPEC-24: Username Enumeration (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
WSO2WSO2 API Manager
  • Default status: unaffected
  • 0 up to but excluding 3.1.0 (unknown)
  • 3.1.0 up to but excluding 3.1.0.310 (affected)
  • 3.2.0 up to but excluding 3.2.0.401 (affected)
  • 3.2.1 up to but excluding 3.2.1.26 (affected)
  • 4.0.0 up to but excluding 4.0.0.318 (affected)
  • 4.1.0 up to but excluding 4.1.0.180 (affected)
  • 4.2.0 up to but excluding 4.2.0.119 (affected)
  • 4.3.0 up to but excluding 4.3.0.30 (affected)
WSO2WSO2 Identity Server as Key Manager
  • Default status: unaffected
  • 0 up to but excluding 5.10.0 (unknown)
  • 5.10.0 up to but excluding 5.10.0.320 (affected)
WSO2WSO2 Identity Server
  • Default status: unaffected
  • 0 up to but excluding 5.10.0 (unknown)
  • 5.10.0 up to but excluding 5.10.0.326 (affected)
  • 6.0.0 up to but excluding 6.0.0.214 (affected)
  • 6.1.0 up to but excluding 6.1.0.198 (affected)
  • 7.0.0 up to but excluding 7.0.0.67 (affected)
WSO2WSO2 Open Banking IAM
  • Default status: unaffected
  • 0 up to but excluding 2.0.0 (unknown)
  • 2.0.0 up to but excluding 2.0.0.371 (affected)
WSO2WSO2 Open Banking AM
  • Default status: unaffected
  • 0 up to but excluding 2.0.0 (unknown)
  • 2.0.0 up to but excluding 2.0.0.351 (affected)
WSO2WSO2 Carborn Identity Handler
  • Default status: unknown
  • 1.4.0 up to but excluding 1.4.0.15 (affected)
  • 1.4.0 up to but excluding 1.4.0.16 (affected)
  • 1.4.11 up to but excluding 1.4.11.14 (affected)
  • 1.4.37 up to but excluding 1.4.37.1 (affected)
  • 1.6.1 up to but excluding 1.6.1.5 (affected)
  • 1.7.1 up to but excluding 1.7.1.1 (affected)
  • 1.8.6 up to but excluding 1.8.6.5 (affected)
  • 1.8.14 up to but excluding 1.8.14.1 (affected)
  • 1.9.2 up to but excluding 1.9.2.4 (affected)

Timeline

  1. 21 Oct 2026 Published

Weakness

References