Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-7478

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

Medium5.8EPSS 0.24%
Published
Updated
Reserved
Assigned by
WSO2

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.

Scores

CVSS scores of CVE-2024-7478, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium5.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
NVDNVD · Awaiting Analysis3.1Medium5.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.8.

Weakness

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 3.1.0
    • affected 3.1.0 – < 3.1.0.310
    • affected 3.2.0 – < 3.2.0.401
    • affected 3.2.1 – < 3.2.1.26
    • affected 4.0.0 – < 4.0.0.318
    • affected 4.1.0 – < 4.1.0.180
    • affected 4.2.0 – < 4.2.0.119
    • affected 4.3.0 – < 4.3.0.30
  • WSO2 · WSO2 Identity Server as Key Manager

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.320
  • WSO2 · WSO2 Identity Server

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.326
    • affected 6.0.0 – < 6.0.0.214
    • affected 6.1.0 – < 6.1.0.198
    • affected 7.0.0 – < 7.0.0.67
  • WSO2 · WSO2 Open Banking IAM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.371
  • WSO2 · WSO2 Open Banking AM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.351
  • WSO2 · WSO2 Carborn Identity Handler

    • affected 1.4.0 – < 1.4.0.15
    • affected 1.4.0 – < 1.4.0.16
    • affected 1.4.11 – < 1.4.11.14
    • affected 1.4.37 – < 1.4.37.1
    • affected 1.6.1 – < 1.6.1.5
    • affected 1.7.1 – < 1.7.1.1
    • affected 1.8.6 – < 1.8.6.5
    • affected 1.8.14 – < 1.8.14.1
    • affected 1.9.2 – < 1.9.2.4

What to do

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

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-7478 badge
[![CVE-2024-7478](https://trackcve.app/badge/CVE-2024-7478.svg)](https://trackcve.app/cve/CVE-2024-7478)

Record last updated .