CVE-2025-13736 Vulnerability Analysis & Exploit Details

CVE-2025-13736
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2025-13736 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-13736 Details

Status: Analyzed

Last updated: 🕢 12 Aug 2026, 19:36 UTC
Originally published on: 🕗 06 Aug 2026, 08:16 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

ed10eef1-636d-4fbe-9993-6890dfa878f8

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-13736 Vulnerability Summary

CVE-2025-13736: 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.

Assessing the Risk of CVE-2025-13736

Access Complexity Graph

The exploitability of CVE-2025-13736 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-13736

CVE-2025-13736 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-13736, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-13736, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-13736 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2025-13736 poses no threat to data integrity.
  • Availability: None
    CVE-2025-13736 does not impact system availability.

CVE-2025-13736 References

External References

CWE Common Weakness Enumeration

CWE-203

CAPEC Common Attack Pattern Enumeration and Classification

  • Black Box Reverse Engineering CAPEC-189 An adversary discovers the structure, function, and composition of a type of computer software through black box analysis techniques. 'Black Box' methods involve interacting with the software indirectly, in the absence of direct access to the executable object. Such analysis typically involves interacting with the software at the boundaries of where the software interfaces with a larger execution environment, such as input-output vectors, libraries, or APIs. Black Box Reverse Engineering also refers to gathering physical side effects of a hardware device, such as electromagnetic radiation or sounds.

Vulnerable Configurations

  • cpe:2.3:a:wso2:api_manager:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.181:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.181:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.267:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.267:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.278:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.278:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.293:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.293:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.320:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.320:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.322:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.322:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.331:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.331:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.345:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.345:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.347:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.347:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.1.0.349:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.1.0.349:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.226:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.226:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.278:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.278:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.351:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.351:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.368:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.368:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.384:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.384:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.397:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.397:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.401:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.401:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.408:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.408:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.413:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.413:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.415:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.415:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.422:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.422:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.427:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.427:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.432:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.432:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.433:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.433:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.434:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.434:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.435:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.435:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.446:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.446:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.450:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.450:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:3.2.0.453:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:3.2.0.453:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.168:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.168:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.217:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.217:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.269:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.269:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.280:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.280:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.293:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.293:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.305:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.305:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.310:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.310:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.318:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.318:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.319:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.319:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.334:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.334:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.355:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.355:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.368:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.368:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.370:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.370:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.373:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.373:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.10.0.284:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.10.0.284:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.10.0.300:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.10.0.300:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.10.0.379:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.10.0.379:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.11.0.321:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.11.0.321:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.11.0.329:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.11.0.329:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:5.11.0.426:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:5.11.0.426:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.0.0.171:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.0.0.171:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.0.0.179:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.0.0.179:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.0.0.249:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.0.0.249:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.0.0.253:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.0.0.253:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.1.0.128:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.1.0.128:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.1.0.136:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.1.0.136:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.1.0.248:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.1.0.248:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:6.1.0.254:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:6.1.0.254:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.0.0.121:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.0.0.121:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.0.0.124:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.0.0.124:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.0.0.131:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.0.0.131:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.1.0.26:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.1.0.26:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.1.0.28:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.1.0.28:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.1.0.31:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.1.0.31:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server:7.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server:7.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0.280:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0.280:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0.296:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0.296:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_am:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_am:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_am:2.0.0.313:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_am:2.0.0.313:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_am:2.0.0.328:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_am:2.0.0.328:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_am:2.0.0.342:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_am:2.0.0.342:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_iam:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_iam:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_iam:2.0.0.318:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_iam:2.0.0.318:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_iam:2.0.0.333:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_iam:2.0.0.333:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:open_banking_iam:2.0.0.348:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:open_banking_iam:2.0.0.348:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-13736: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-90555 – vLLM versions before 0.28.0 fail to validate audio sample rate headers in the transcription endpoint, allowing authenticated clients to bypass dura...
  • CVE-2026-90554 – vLLM versions >=0.10.2 and <0.28.0 do not apply any audio decode-size or duration limit when extracting audio from video input for NanoNemotronVL m...
  • CVE-2026-90553 – vLLM before 0.28.0 contains a remote code execution vulnerability in the LlavaOnevision2 processor loader that ignores the trust_remote_code parame...
  • CVE-2026-90552 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the Playlists_schedules/list.json.php a...
  • CVE-2026-90551 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the video_from_program API endpoint, al...