dbcve.org
Identity ServerApplication · Wso2

CVE-2025-1396

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses. Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a username enumeration vulnerability in WSO2 products (multiple products affected) when Multi-Attribute Login is enabled. The system returns distinct error messages for existing vs. non-existing users, allowing attackers to confirm valid usernames through observable differences in authentication failure responses, regardless of the validate_username configuration setting.

MitigationConfigure the system to return uniform, generic error messages for all failed authentication attempts rather than different messages based on user existence. Alternatively, disable Multi-Attribute Login if not required or apply vendor-supplied patches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity ServerApplication
Affected:= 5.10.0= 5.11.0= 6.0.0= 6.1.0
Identity Server As Key ManagerApplication
Affected:= 5.10.0
Open Banking IamApplication
Affected:= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WSO2 product and version
    Locate the product's version file or admin console. For WSO2 Identity Server, check the <IS_HOME>/repository/components/VERSION file or the About section in the management console.
    Affected if The installed version matches 5.10.0, 5.11.0, 6.0.0, or 6.1.0 for Identity Server; 5.10.0 for Identity Server As Key Manager; or 2.0.0 for Open Banking IAM.
  2. Confirm Multi-Attribute Login is enabled
    Check the application-authentication.xml configuration file located in <IS_HOME>/repository/conf/identity/ for the MultiAttributeLogin property. Look for a LoginCfg element with enabled set to true.
    Affected if Multi-Attribute Login is enabled in the authentication configuration.
  3. Verify validate_username setting
    In the same application-authentication.xml file, locate the validate_username parameter within the MultiAttributeLogin configuration. Note its current value.
    Affected if The validate_username setting is present and set to either true or false - note that this vulnerability is exploitable regardless of this setting.
  4. Test authentication response for valid vs invalid username
    Submit two login attempts: one with a known-valid username and one with a random nonexistent username. Compare the error messages returned by the authentication endpoint in both responses.
    Affected if The error messages differ between the two attempts, with one explicitly indicating the user does not exist versus a generic authentication failure.

You are affected if you run a listed WSO2 product version with Multi-Attribute Login enabled and your system returns different error messages for existing versus nonexistent usernames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the system to return uniform, generic error messages for all failed authentication attempts rather than different messages based on user existence. Alternatively, disable Multi-Attribute Login if not required or apply vendor-supplied patches.

Fix this in Identity Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1396 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data