Cross-Site Scripting (XSS) in Splunk Enterprise (CVE-2025-20367)
Summary
Cross-site scripting in Splunk Enterprise (CVE-2025-20367). Confidential information can be exposed externally. Exploitable via dataset.command.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-20367 has been found in Splunk Enterprise.
Attackers can target a specific entry point like dataset.command over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Splunk Enterprise CVE-2025-20367" on the vendor's site.
CVE-2025-20367 (Splunk Enterprise) — CWE-79 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: dataset.command
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Splunk Enterprise. Attackers reach the vulnerable code path via dataset.command.
Check the vendor advisory for the affected versions of Splunk Enterprise. Attack surface: dataset.command.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Splunk Enterprise を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch psirt@cisco.com