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.
Published: 2026-10-21
Score: 5.8 Medium
EPSS: n/a
KEV: No
Impact: User Account Enumeration
Action: Apply Patch
AI Analysis

Impact

When a WSO2 product is configured to use an external user store, the authentication mechanism fails to hide whether a given username is valid. As a result, an attacker who can send repeated authentication attempts can discover which usernames exist, enabling targeted brute‑force attacks, phishing, and other credential‑based compromises that could lead to sensitive data exposure and reputational harm.

Affected Systems

All versions of the listed WSO2 products—WSO2 API Manager, WSO2 Carbon Identity Handler, WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 Open Banking AM, and WSO2 Open Banking IAM—are affected when they are configured to use an external user store. No specific version numbers are supplied; the issue applies to all impacted configurations.

Risk and Exploitability

The vulnerability carries a medium CVSS score of 5.8, with no EPSS score available and it is not listed in the CISA KEV catalog. The most likely attack vector is remote authentication over the network, requiring the ability to send authentication requests to the affected endpoint. An attacker can iteratively test usernames to build a full list of valid accounts, significantly reducing the effort needed for subsequent credential‑guessing or social‑engineering attacks.

Generated by OpenCVE AI on October 22, 2026 at 00:55 UTC.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Implement the fixes provided in the WSO2 security advisory by following the instructions at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3606/#solution.
  • If an immediate patch is not possible, block or rate‑limit authentication attempts against external user stores to prevent brute‑force enumeration.
  • Change the authentication error messages to a generic response that does not reveal username validity, thereby mitigating enumeration.

Generated by OpenCVE AI on October 22, 2026 at 00:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 22 Oct 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Wso2 identity Server
Vendors & Products Wso2 identity Server

Wed, 21 Oct 2026 14:00:00 +0000

Type Values Removed Values Added
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.
Title Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery
First Time appeared Wso2
Wso2 wso2 Api Manager
Wso2 wso2 Carborn Identity Handler
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Weaknesses CWE-204
CPEs cpe:2.3:a:wso2:wso2_api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_carborn_identity_handler:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server_as_key_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_am:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_iam:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 wso2 Api Manager
Wso2 wso2 Carborn Identity Handler
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
References
Metrics cvssV3_1

{'score': 5.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N'}


Subscriptions

Wso2 Identity Server Wso2 Api Manager Wso2 Carborn Identity Handler Wso2 Identity Server Wso2 Identity Server As Key Manager Wso2 Open Banking Am Wso2 Open Banking Iam
cve-icon MITRE

Status: PUBLISHED

Assigner: WSO2

Published:

Updated: 2026-10-21T13:49:07.839Z

Reserved: 2024-08-05T07:38:19.343Z

Link: CVE-2024-7478

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-21T14:17:06.147

Modified: 2026-10-21T18:37:59.557

Link: CVE-2024-7478

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-22T01:30:06Z

Weaknesses
  • CWE-204

    Observable Response Discrepancy