Skip to content
Fencer Intel
low 3.7

CVE-2025-13736 json

Username Enumeration via Login Interface in Multiple WSO2 Products Allows User Account Discovery

published 3mo ago modified last mo. also EUVD-2025-210626

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts. For valid users, the server resolves and displays their canonical username, while for non-existent users, it echoes the original input. This occurs regardless of the validate_username configuration.

The discovery of valid usernames can increase the risk of brute force attacks, social engineering attacks, and targeted information leakage. Attackers can leverage this information to craft more effective phishing campaigns or social engineering tactics to compromise user accounts or extract sensitive data.

Patch / fix

  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.371
  • WSO2 WSO2 Identity Server 5.10.0.380, 5.11.0.427, 6.0.0.254, 6.1.0.255, 7.0.0.132, 7.1.0.40, 7.2.0.2
  • WSO2 WSO2 Open Banking AM 2.0.0.400
  • WSO2 WSO2 API Manager 3.1.0.351, 3.2.0.455, 4.0.0.375
  • WSO2 WSO2 Open Banking IAM 2.0.0.420

Is CVE-2025-13736 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • WSO2 WSO2 Identity Server as Key Manager
  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Open Banking AM
  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Open Banking IAM

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.