CVE-2025-20320
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, and Splunk Cloud Platform versions below 9.3.2411.107, 9.3.2408.117, and 9.2.2406.121, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the `User Interface - Views` configuration page that could potentially lead to a denial of service (DoS).The user could cause the DoS by exploiting a path traversal vulnerability that allows for deletion of arbitrary files within a Splunk directory. The vulnerability requires the low-privileged user to phish the administrator-level victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.
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 confidenceA path traversal vulnerability in Splunk Enterprise and Cloud Platform's User Interface - Views configuration allows low-privileged users to craft malicious payloads that can delete arbitrary files within the Splunk directory, leading to denial of service. The attacker must-phish an administrator to initiate the request in their browser, as the low-privileged user cannot exploit it at will.
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.3>= 9.2.2406, < 9.2.2406.121>= 9.3.2408, < 9.3.2408.117>= 9.3.2411, < 9.3.2411.107CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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 Splunk Enterprise versionRun the command: splunk version or access the UI at Settings > About > Product Info to view the installed versionAffected if The installed version falls within any of these ranges: >= 9.1.0 and < 9.1.10, >= 9.2.0 and < 9.2.7, >= 9.3.0 and < 9.3.5, or >= 9.4.0 and < 9.4.3
-
Check Splunk Cloud Platform versionIn Splunk Cloud, navigate to Settings > System > Product Info or use the cloud diagnostics endpoint to retrieve the version numberAffected if The installed version is >= 9.2.2406 and < 9.2.2406.121, >= 9.3.2408 and < 9.3.2408.117, or >= 9.3.2411 and < 9.3.2411.107
-
Verify Views configuration accessConfirm whether low-privileged non-admin users have access to the Views UI section by reviewing Roles in Settings > Access Controls > Roles and checking if any custom roles grant XML view editing capabilitiesAffected if Non-admin users have access to the Views configuration interface, as the path traversal exploit targets this component when triggered by an administrator session
Your environment is affected if Splunk Enterprise is running version 9.1.0-9.1.9, 9.2.0-9.2.6, 9.3.0-9.3.4, or 9.4.0-9.4.2, or Splunk Cloud Platform is running version 9.2.2406-9.2.2406.120, 9.3.2408-9.3.2408.116, or 9.3.2411-9.3.2411.106, and low-privileged users have access to the Views configuration UI.
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.2.2406.121
Upgrade to Splunk Enterprise versions 9.4.3, 9.3.5, 9.2.7, or 9.1.10 (and equivalent Cloud Platform versions 9.3.2411.107, 9.3.2408.117, or 9.2.2406.121) to patch the path traversal vulnerability.
Splunk Enterprise: 9.1.10, 9.2.7, 9.3.5, or 9.4.3 (depending on current branch) | Splunk Cloud Platform: 9.2.2406.121, 9.3.2408.117, or 9.3.2411.107
- Determine current Splunk version by navigating to Settings > About > Product Info in Splunk Web, or running `./splunk --version` from the installation directory
- For Splunk Enterprise: Identify which version branch is in use (9.1.x, 9.2.x, 9.3.x, or 9.4.x)
- Upgrade to the fixed version for the respective branch: 9.1.10 for 9.1.x, 9.2.7 for 9.2.x, 9.3.5 for 9.3.x, or 9.4.3 for 9.4.x
- Download the upgrade from splunk.com/download or use the tar/zip appropriate for the environment
- Review Splunk upgrade documentation for backup and migration requirements before proceeding
- Execute the upgrade following standard Splunk upgrade procedures
- For Splunk Cloud Platform: Contact Splunk Support to request the patched version upgrade (9.2.2406.121, 9.3.2408.117, or 9.3.2411.107 depending on current version)
- Verify the upgrade was successful and the Splunk Web interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20320 — 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-20320 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