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

> Attackers can enumerate valid usernames via self-registration error messages, facilitating targeted attacks against WSO2 identity products.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-6cgx-wc6q-rrj4

## What is CVE-2025-5802?

CVE-2025-5802 is a medium-severity vulnerability in WSO2 API Control Plane, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2025-5802?


## How do I fix CVE-2025-5802?

No fix has been published for CVE-2025-5802 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5802 being exploited?

There is no known exploitation of CVE-2025-5802 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5802 and fix it if it is affected.

What it is: CVE-2025-5802 is a medium-severity vulnerability in WSO2 API Control Plane, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5802 in the wild and no public exploit code.

Affected product: WSO2 API Control Plane. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5802/ (Markdown: https://insights.sbomify.com/CVE-2025-5802/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5802
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5802
- OSV: https://osv.dev/vulnerability/CVE-2025-5802

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5802/
Summaries are generated and may contain mistakes; the official description above is the record.