# CVE-2025-1396: Username Enumeration in Multiple WSO2 Products with Multi-Attribute Login Enabled

> Attackers can enumerate valid usernames in WSO2 products when Multi-Attribute Login is enabled, facilitating targeted attacks.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/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:** Yes
- **Published:** 26 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** CLEANSTART-2026-WA25182, GHSA-w82p-r9vw-4rg5

## What is CVE-2025-1396?

CVE-2025-1396 is a low-severity vulnerability in Wso2 Identity Server, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-203 (Observable Discrepancy)

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

2 open source packages ship an affected version, including org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt` | Maven | All versions to 7.8.103 | None |
| `org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt` | Maven | All versions to 7.8.103 | None |

Products: Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Iam.

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

Apply the vendor's patch.

## Is CVE-2025-1396 being exploited?

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

## Other vulnerabilities in Wso2 Identity Server

- [CVE-2016-4311](https://insights.sbomify.com/CVE-2016-4311/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-10470](https://insights.sbomify.com/CVE-2025-10470/): Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability (high 8.6)
- [CVE-2025-12107](https://insights.sbomify.com/CVE-2025-12107/): Server-Side Template Injection via Velocity Template Engine in Multiple WSO2 Products Allows Remote Code Execution (high 8.4)
- [CVE-2016-4312](https://insights.sbomify.com/CVE-2016-4312/): XML external entity in n/a (high 7.5)
- [CVE-2025-10908](https://insights.sbomify.com/CVE-2025-10908/): Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1396 is a low-severity vulnerability in Wso2 Identity Server, published on 26 Sep 2025. 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-1396 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt (Maven): affected all versions up to 7.8.103; no fix listed
- org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt (Maven): affected all versions up to 7.8.103; no fix listed

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-1396/ (Markdown: https://insights.sbomify.com/CVE-2025-1396/index.md)
```

## Sources

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

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