CVE-2025-5802
Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery
MEDIUM
5.3
CVSS Score
Published: September 15, 2026 at 09:53 AM UTC
Updated: September 18, 2026 at 07:29 PM UTC
10 products affected across 1 vendorAPI ManagerIdentity ServerIdentity Server As Key Manager
Using WSO2 API Manager by WSO2?
Get instant alerts when new vulnerabilities affect WSO2 API Manager - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Affected range stops below 4.5.0.56, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.18, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.5.0 (unknown)
3.1.0 ≤ v < 3.1.0.3543.2.0 ≤ v < 3.2.0.4583.2.0 ≤ v < 3.2.0.4783.2.1 ≤ v < 3.2.1.964.0.0 ≤ v < 4.0.0.3794.1.0 ≤ v < 4.1.0.2624.2.0 ≤ v < 4.2.0.2004.3.0 ≤ v < 4.3.0.1124.4.0 ≤ v < 4.4.0.724.5.0 ≤ v < 4.5.0.554.6.0 ≤ v < 4.6.0.173.1.03.2.03.2.14.0.04.1.04.2.04.3.04.4.04.5.04.6.0
Affected range stops below 3.1.0.354, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.0.458, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.0.478, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.1.96, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.0.379, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.0.262, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.0.200, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.0.112, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.4.0.72, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.0.55, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.17, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.1.0 (unknown)
Affected range stops below 5.17.5.332, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.18.187.330, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in x (unaffected)
5.17.5 ≤ v < 5.17.5.3325.18.187 ≤ v < 5.18.187.3305.23.8 ≤ v < 5.23.8.2135.25.92 ≤ v < 5.25.92.1677.0.78 ≤ v < 7.0.78.1625.17.55.18.1875.23.85.25.927.0.78
Affected range stops below 5.17.5.332, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.18.187.330, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.23.8.213, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.25.92.167, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.78.162, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in x (unaffected)
5.10.0 ≤ v < 5.10.0.3835.11.0 ≤ v < 5.11.0.4306.0.0 ≤ v < 6.0.0.2576.1.0 ≤ v < 6.1.0.2346.1.0 ≤ v < 6.1.0.2577.0.0 ≤ v < 7.0.0.1337.1.0 ≤ v < 7.1.0.417.2.0 ≤ v < 7.2.0.35.10.05.11.06.0.06.1.07.0.07.1.07.2.0
Affected range stops below 5.10.0.383, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11.0.430, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.0.257, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0.234, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0.257, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.0.133, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.1.0.41, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.0.3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.0 (unknown)
5.10.0 ≤ v < 5.10.0.3745.10.0
Affected range stops below 5.10.0.374, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.0 (unknown)
2.0.0 ≤ v < 2.0.0.4032.0.0
Affected range stops below 2.0.0.403, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2.0.0 (unknown)
2.0.0 ≤ v < 2.0.0.4232.0.0
Affected range stops below 2.0.0.423, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2.0.0 (unknown)
Affected range stops below 4.5.0.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.17, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.5.0 (unknown)
Affected range stops below 4.5.0.55, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.17, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.5.0 (unknown)
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (1)
Vendor Advisory
Source: cverecord
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4227/SSVC — Action Prioritization
SSVCNo known exploitAutomatablePartial impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
5.3MEDIUMWSO2
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- LOW
- Integrity
- NONE
- Availability
- NONE
Vector?
Quick Info
StatusDEFERRED
CWE
CWE-203
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card