CVE-2025-20369 Vulnerability Analysis & Exploit Details

CVE-2025-20369
Vulnerability Scoring

4.6
/10
Medium Risk

The vulnerability CVE-2025-20369 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2025-20369 Details

Status: Analyzed

Last updated: 🕗 08 Oct 2025, 20:24 UTC
Originally published on: 🕔 01 Oct 2025, 17:15 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

psirt@cisco.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-20369 Vulnerability Summary

CVE-2025-20369: In Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.108, 9.3.2408.118 and 9.2.2406.123, a low privilege user that does not hold the "admin" or "power" Splunk roles could perform an extensible markup language (XML) external entity (XXE) injection through the dashboard tab label field. The XXE injection has the potential to cause denial of service (DoS) attacks.

Assessing the Risk of CVE-2025-20369

Access Complexity Graph

The exploitability of CVE-2025-20369 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-20369

CVE-2025-20369 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-20369, 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-20369, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-20369 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2025-20369 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2025-20369 may slightly degrade system performance without fully affecting service availability.

CVE-2025-20369 References

External References

CWE Common Weakness Enumeration

CWE-611

CAPEC Common Attack Pattern Enumeration and Classification

  • Data Serialization External Entities Blowup CAPEC-221 This attack takes advantage of the entity replacement property of certain data serialization languages (e.g., XML, YAML, etc.) where the value of the replacement is a URI. A well-crafted file could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.

Vulnerable Configurations

  • cpe:2.3:a:splunk:splunk:9.2.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.2.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.2.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.100:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.100:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.106:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.106:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.107:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.107:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.108:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.108:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.111:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.111:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.113:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.113:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.118:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.118:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.119:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.119:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.121:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.121:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.122:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.2.2406.122:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.100:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.100:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.101:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.101:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.103:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.103:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.104:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.104:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.107:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.107:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.111:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.111:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.112:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.112:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.113:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.113:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.114:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.114:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.117:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.117:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.102:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.102:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.103:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.103:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.104:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.104:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.107:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.107:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-20369: 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-2025-62728 – SQL injection vulnerability in Hive Metastore Server (HMS) when processing delete column statistics requests via the Thrift APIs. The vulnerability...
  • CVE-2025-59390 – Apache Druid’s Kerberos authenticator uses a weak fallback secret when the `druid.auth.authenticator.kerberos.cookieSignatureSecret` configuration ...
  • CVE-2025-13735 – Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program fi...
  • CVE-2025-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...