CVE-2025-5802

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

Security Advisory WSO2-2025-4227/CVE-2025-5802 - WSO2 Security and Compliance Documentation

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

Vendor Advisories for CVE-2025-5802(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 19:37 UTCEG score recompute
  2. 2026-09-19 19:37 UTCGHSA enrichment
  3. 2026-09-19 15:42 UTCEPSS rescore
  4. 2026-09-18 19:29 UTCEG score recompute
  5. 2026-09-18 19:29 UTCGHSA enrichment
  6. 2026-09-18 19:27 UTCEPSS rescore
  7. 2026-09-18 14:15 UTCEG score recompute
  8. 2026-09-18 14:15 UTCGHSA enrichment
  9. 2026-09-17 19:30 UTCEPSS rescore
  10. 2026-09-17 13:58 UTCEG score recompute
  11. 2026-09-17 13:58 UTCGHSA enrichment
  12. 2026-09-16 14:07 UTCEPSS rescore
  13. 2026-09-16 13:49 UTCEG score recompute
  14. 2026-09-16 13:49 UTCGHSA enrichment
  15. 2026-09-15 13:33 UTCEG score recompute
  16. 2026-09-15 13:33 UTCGHSA enrichment
  17. 2026-09-15 12:53 UTCEG score recompute
  18. 2026-09-15 12:53 UTCGHSA enrichment
  19. 2026-09-15 10:28 UTCEG score recompute
  20. 2026-09-15 09:58 UTCEG score recompute
  21. 2026-09-15 09:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-5802?
CVE-2025-5802 is a medium vulnerability published on September 15, 2026. 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.…
When was CVE-2025-5802 disclosed?
CVE-2025-5802 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-5802 actively exploited?
CVE-2025-5802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.2% of all scored CVEs.
What is the CVSS score of CVE-2025-5802?
CVE-2025-5802 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2025-5802?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5802, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-5802

Explore →

Is Your Infrastructure Affected by CVE-2025-5802?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs