CVE-2025-20232: Risky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in Splunk Enterprise
In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 and 9.1.2308.212, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on the “/app/search/search“ endpoint through its “s“ parameter. <br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-20232?
CVE-2025-20232 is classified as a low-severity vulnerability affecting certain Splunk versions.
How do I fix CVE-2025-20232?
To fix CVE-2025-20232, upgrade to Splunk Enterprise version 9.3.3 or higher, or Splunk Cloud Platform version 9.3.2408.103 or higher.
Who is affected by CVE-2025-20232?
CVE-2025-20232 affects low-privileged users in Splunk Enterprise and Splunk Cloud who lack admin or power roles.
What versions of Splunk are impacted by CVE-2025-20232?
CVE-2025-20232 impacts Splunk Enterprise versions below 9.3.3 and Splunk Cloud Platform versions below 9.3.2408.103.
What is the nature of the vulnerability in CVE-2025-20232?
CVE-2025-20232 allows a low-privileged user to run a saved search that could potentially exploit system resources.