CVE-2025-20300
BaseFortify
Publication date: 2025-07-07
Last updated on: 2025-07-21
Assigner: Cisco Systems, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| splunk | splunk | From 9.1.0 (inc) to 9.1.9 (exc) |
| splunk | splunk | From 9.2.0 (inc) to 9.2.6 (exc) |
| splunk | splunk | From 9.3.0 (inc) to 9.3.5 (exc) |
| splunk | splunk | From 9.4.0 (inc) to 9.4.2 (exc) |
| splunk | splunk_cloud_platform | From 9.2.2406 (inc) to 9.2.2406.118 (exc) |
| splunk | splunk_cloud_platform | From 9.3.2408 (inc) to 9.3.2408.112 (exc) |
| splunk | splunk_cloud_platform | From 9.3.2411 (inc) to 9.3.2411.103 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-20300 is a medium-severity vulnerability in Splunk Enterprise and Splunk Cloud Platform where a low-privileged user who does not have 'admin' or 'power' roles but has read-only access to a specific alert can suppress that alert when it triggers. This is due to improper access control in the Splunk Web component, allowing unauthorized alert suppression. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users with limited privileges to suppress alerts that they should only be able to view. This could lead to missed or ignored alerts, potentially causing delayed responses to important security or operational events, thereby impacting the reliability of monitoring and incident response. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
No detection methods are currently available for this vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Splunk Enterprise to versions 9.4.2, 9.3.5, 9.2.6, or 9.1.9, or upgrade Splunk Cloud Platform to the corresponding fixed versions. As a workaround, disabling Splunk Web may reduce exposure. [1]