CVE-2025-13736 — Observable Discrepancy in WSO2 Api Manager
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Identity Server, WSO2 Identity Server As Key Manager…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Manager | ≥ 3.1.0 and < 3.1.0.351≥ 3.2.0 and < 3.2.0.455≥ 4.0.0 and < 4.0.0.375 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Identity Server | ≥ 5.10.0 and < 5.10.0.380≥ 5.11.0 and < 5.11.0.427≥ 6.0.0 and < 6.0.0.254≥ 6.1.0 and < 6.1.0.255≥ 7.0.0 and < 7.0.0.132≥ 7.1.0 and < 7.1.0.40≥ 7.2.0 and < 7.2.0.2 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Identity Server As Key Manager | ≥ 5.10.0 and < 5.10.0.371 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Open Banking Am | ≥ 2.0.0 and < 2.0.0.400 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Open Banking Iam | ≥ 2.0.0 and < 2.0.0.420 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 3.7 | CVSS 3.1 | Low | 2.2 | 1.4 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for anomalous data read/export volumes and access to sensitive records.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- CVSS changed · 3.7
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 7d
- Low CVE-2025-13166 Username Enumeration via SMS OTP Flow in WSO2 Identity Server Allows User Account Discovery Sep 15, 2026
- High CVE-2025-12737 OS Command Injection in WSO2 Api Control Plane Sep 3, 2026
- High CVE-2026-3416 Use of Insufficiently Random Values in WSO2 Api Control Plane Sep 3, 2026
- Critical CVE-2026-5430 WSO2 Multiple Products Path Traversal Vulnerability KEV Aug 6, 2026
- Critical CVE-2026-1728 Improper Privilege Management in WSO2 Api Control Plane Aug 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-13736 is "Observable Discrepancy in WSO2 Api Manager", rated Low. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.7 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.