WSO2's Input Validation Management Service contains Observable Discrepancy when Multi-Attribute Login is enabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-1396: 0.25% estimated exploitation activity in the next 30 days; percentile 16.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 validateusername 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. There is a fix available in version 7.8.491, however it has not been published to the Maven registry.

Published by the source

26 Sep 2025, 09:31 UTC

Last modified by the source

8 Oct 2025, 19:18 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w82p-r9vw-4rg5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-1396

Advisory: WSO2's Input Validation Management Service contains Observable Discrepancy when Multi-Attribute Login is enabled
IDs: CVE-2025-1396, GHSA-w82p-r9vw-4rg5
Record: https://patchnext.com/advisories/cve-2025-1396 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt: affected <= 7.8.103

## Suggested inspection (read-only)
- Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w82p-r9vw-4rg5 (GitHub-reviewed advisory GHSA-w82p-r9vw-4rg5 lists affected ranges: Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt >=0 <=7.8.103)

Commands are suggestions: review each one before running it.