CVE-2025-1396Network attack vector

Username enumeration via distinct login errors

Published Sep 26, 2025 · Updated Sep 26, 2025

Username enumeration in affected WSO2 identity products allows remote attackers to identify valid accounts through login-response differences. With Multi-Attribute Login enabled, the authentication flow returns "User does not exist" directly to the login form even when validate_username disables that disclosure. No authentication or user interaction is required, but exposure depends on Multi-Attribute Login being enabled; the result is account-identifier disclosure that can support brute-force or targeted phishing.

CVSS severity3.7
Low
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Username enumeration in affected WSO2 identity products allows remote attackers to identify valid accounts through login-response differences. With Multi-Attribute Login enabled, the authentication flow returns "User does not exist" directly to the login form even when validate_username disables that disclosure. No authentication or user interaction is required, but exposure depends on Multi-Attribute Login being enabled; the result is account-identifier disclosure that can support brute-force or targeted phishing.

The record

CVE
CVE-2025-1396
Published
Sep 26, 2025
Updated
Sep 26, 2025
Vendor
WSO2
Product
WSO2 Identity Server
Classifications
CWE-203, T1087
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 26, 2025CVE publishedPublication date reported by the CVE source.
  2. Sep 26, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.10.0 <5.10.0.346
  2. Affected versionversion=5.11.0 <5.11.0.395
  3. Affected versionversion=6.0.0 <6.0.0.231
  4. Affected versionversion=6.1.0 <6.1.0.223

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WSO2 · WSO2 Identity Serverversion=5.10.0 <5.10.0.346; version=5.11.0 <5.11.0.395; version=6.0.0 <6.0.0.231; version=6.1.0 <6.1.0.223
WSO2 · WSO2 Open Banking IAMversion=2.0.0 <2.0.0.390
WSO2 · WSO2 Identity Server as Key Managerversion=5.10.0 <5.10.0.339

Published CVSS scores

3.7WSO2 LLCCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-203Observable Discrepancy
T1087Account Discovery

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo