Username Enumeration in Multiple WSO2 Products with Multi-Attribute Login Enabled
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| WSO2 | WSO2 Identity Server | unaffected |
|
||||||||||||||||||
| WSO2 | WSO2 Open Banking IAM | unaffected |
|
||||||||||||||||||
| WSO2 | WSO2 Identity Server as Key Manager | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Wso2 | Identity Server | — |
| Wso2 | Identity Server As Key Manager | — |
| Wso2 | Open Banking Iam | — |
Vendor Solution
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-3983/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-3983/#solution
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-31223 | A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses. Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system. |
Github GHSA |
GHSA-w82p-r9vw-4rg5 | WSO2's Input Validation Management Service contains Observable Discrepancy when Multi-Attribute Login is enabled |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.251% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wso2:identity_server:5.10.0:*:*:*:*:*:*:* cpe:2.3:a:wso2:identity_server:5.11.0:*:*:*:*:*:*:* cpe:2.3:a:wso2:identity_server:6.0.0:*:*:*:*:*:*:* cpe:2.3:a:wso2:identity_server:6.1.0:*:*:*:*:*:*:* cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0:*:*:*:*:*:*:* cpe:2.3:a:wso2:open_banking_iam:2.0.0:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wso2
Wso2 identity Server Wso2 identity Server As Key Manager Wso2 open Banking Iam |
|
| Vendors & Products |
Wso2
Wso2 identity Server Wso2 identity Server As Key Manager Wso2 open Banking Iam |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-203 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses. Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system. | |
| Title | Username Enumeration in Multiple WSO2 Products with Multi-Attribute Login Enabled | |
| References |
| |
| Metrics |
cvssV3_1
|