CVE-2025-20319
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSplunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10 contain a remote command execution vulnerability. Users with roles possessing both the `edit_scripted` and `list_inputs` capabilities can execute arbitrary commands due to improper input sanitization in scripted input file handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.1.0, < 9.1.10>= 9.2.0, < 9.2.7>= 9.3.0, < 9.3.5>= 9.4.0, < 9.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Splunk Enterprise versionRun 'splunk version' from the Splunk bin directory, or log into the Splunk web interface and navigate to Settings > About > VersionAffected if The installed version is below 9.1.10, 9.2.7, 9.3.5, or 9.4.3 (any of the four affected version ranges)
-
Identify roles with the edit_scripted capabilityIn Splunk web, go to Settings > Users, Authentication, and Authorization > Roles. Review each role's capabilities section and note which roles have 'edit_scripted' enabled. Alternatively, run 'splunk btool roles list' from the command line.Affected if Any role assigned to users has the edit_scripted capability enabled
-
Identify roles with the list_inputs capabilityIn Splunk web, go to Settings > Users, Authentication, and Authorization > Roles. Review each role's capabilities section and note which roles have 'list_inputs' enabled. Alternatively, run 'splunk btool roles list' from the command line.Affected if Any role assigned to users has the list_inputs capability enabled
-
Confirm if any user account has BOTH capabilitiesCross-reference the results from steps 2 and 3. Determine if any single user possesses both edit_scripted and list_inputs capabilities through their assigned role or roles.Affected if A user account has a role (or combination of roles) that grants both edit_scripted AND list_inputs capabilities
-
Check for configured scripted inputsIn Splunk web, go to Settings > Inputs > Scripts to see if any scripted inputs are configured. Alternatively, search for [script] stanzas in $SPLUNK_HOME/etc/system/local/inputs.conf or relevant app local inputs.conf files.Affected if Scripted inputs are configured and enabled in the Splunk environment
You are affected if your Splunk Enterprise version is in any of the vulnerable ranges AND at least one user account possesses both the edit_scripted and list_inputs capabilities AND scripted inputs are configured in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.1.109.2.79.3.5
Upgrade Splunk Enterprise to version 9.4.3, 9.3.5, 9.2.7, 9.1.10 or later. Additionally, audit roles to remove the `edit_scripted` capability from users who do not require it, limiting exposure.
9.1.10 (for 9.1.x branch), 9.2.7 (for 9.2.x branch), 9.3.5 (for 9.3.x branch), or 9.4.3 (for 9.4.x branch)
- Identify the current Splunk Enterprise version by navigating to Settings > About or running 'splunk version' CLI
- Determine which version branch (9.1.x, 9.2.x, 9.3.x, or 9.4.x) the current installation is on
- For 9.1.x branch: upgrade to version 9.1.10 or later
- For 9.2.x branch: upgrade to version 9.2.7 or later
- For 9.3.x branch: upgrade to version 9.3.5 or later
- For 9.4.x branch: upgrade to version 9.4.3 or later
- Download the target version from splunk.com or your Splunk license partner
- Review Splunk Upgrade Planning documentation before proceeding
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data