dbcve.org
SplunkApplication

CVE-2025-20367

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-01
Fix available
A fix is available. Upgrade to 9.2.8 / 9.2.2406.122 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
In Splunk Enterprise versions below 9.4.4, 9.3.6 and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.109, 9.3.2408.119 and 9.2.2406.122, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could craft a malicious payload through the `dataset.command` parameter of the `/app/search/table` endpoint, which could result in execution of unauthorized JavaScript code in the browser of a user.

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 confidence

A reflected XSS vulnerability exists in Splunk Enterprise and Cloud Platform where a low-privileged user can inject malicious JavaScript through the dataset.command parameter of the /app/search/table endpoint, causing arbitrary code execution in the browser of users who interact with the crafted payload.

MitigationUpgrade Splunk Enterprise to version 9.4.4, 9.3.6, 9.2.8 or higher; or upgrade Splunk Cloud Platform to version 9.3.2411.109, 9.3.2408.119, 9.2.2406.122 or higher.

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
SplunkApplication
Affected:>= 9.2.0, < 9.2.8>= 9.3.0, < 9.3.6>= 9.4.0, < 9.4.4
Splunk Cloud PlatformApplication
Affected:>= 9.2.2406, < 9.2.2406.122>= 9.3.2408, < 9.3.2408.119>= 9.3.2411, < 9.3.2411.109

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Splunk Enterprise version
    In Splunk Enterprise, go to Settings > About > Version or run the command: splunk version
    Affected if The installed version is 9.2.0 through 9.2.7, 9.3.0 through 9.3.5, or 9.4.0 through 9.4.3 (i.e., it falls within >= 9.2.0 < 9.2.8, >= 9.3.0 < 9.3.6, or >= 9.4.0 < 9.4.4)
  2. Check Splunk Cloud Platform version
    In Splunk Cloud, navigate to Settings > System > About or contact your Splunk Cloud administrator for the platform version information
    Affected if The installed version is 9.2.2406 through 9.2.2406.121, 9.3.2408 through 9.3.2408.118, or 9.3.2411 through 9.3.2411.108 (i.e., it falls within >= 9.2.2406 < 9.2.2406.122, >= 9.3.2408 < 9.3.2408.119, or >= 9.3.2411 < 9.3.2411.109)
  3. Verify access to /app/search/table endpoint
    Attempt to access the endpoint via URL: https://<your-splunk-host>/en-US/app/search/table (the vulnerability exists when this endpoint is reachable and accepts the dataset.command parameter)
    Affected if The endpoint is accessible and processes the dataset.command parameter without proper output encoding

A user is affected if they run a Splunk Enterprise version below 9.2.8, 9.3.6, or 9.4.4, or a Splunk Cloud Platform version below 9.2.2406.122, 9.3.2408.119, or 9.3.2411.109, and the /app/search/table endpoint is accessible to low-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.2.8 / 9.2.2406.122 / 9.3.6 or later
Fixed in 9.2.89.2.2406.1229.3.6
Interim mitigation

Upgrade Splunk Enterprise to version 9.4.4, 9.3.6, 9.2.8 or higher; or upgrade Splunk Cloud Platform to version 9.3.2411.109, 9.3.2408.119, 9.2.2406.122 or higher.

Recommended fix High confidence

Splunk Enterprise: 9.2.8, 9.3.6, or 9.4.4 (and later) | Splunk Cloud Platform: 9.2.2406.122, 9.3.2408.119, or 9.3.2411.109 (and later)

  1. 1. Identify the currently installed Splunk Enterprise or Splunk Cloud Platform version
  2. 2. For Splunk Enterprise: Upgrade to version 9.2.8, 9.3.6, or 9.4.4 (or later) depending on your current major version branch
  3. 3. For Splunk Cloud Platform: Contact Splunk Support to request upgrade to version 9.2.2406.122, 9.3.2408.119, or 9.3.2411.109 (or later) depending on your current deployment
  4. 4. After upgrade, verify the fix by testing that the dataset.command parameter on /app/search/table no longer executes unsanitized JavaScript
  5. 5. ReviewSplunk Enterprise release notes for the target version for any additional security hardening
Caveat Review Splunk upgrade documentation for compatibility considerations; major version upgrades may require migration planning

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20367 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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