Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

Stored XSS in Splunk saved search error messages and job inspection details

IdentifiersCVE-2025-20368CWE-79· Improper Neutralization of Input…

CVE-2025-20368 is a cross-site scripting vulnerability in Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.108, 9.3.2408.118, and 9.2.2406.123. According to the provided content, a low-privileged user without the admin or power Splunk roles can craft a malicious payload through the error messages and job inspection details of a saved search. When another user views the affected saved search information, the payload can execute unauthorized JavaScript in that user’s browser. Based on the described injection point and trigger, this is best characterized as a stored XSS issue affecting Splunk Web presentation of saved search metadata or related diagnostic output.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows attacker-controlled JavaScript to run in the browser context of another Splunk user who views the malicious saved search error or job inspection content. This can enable session theft, access to sensitive data visible to the victim, execution of actions in the victim’s authenticated session, and potential abuse of the victim’s privileges within the Splunk web interface.

Mitigation

If you can’t patch tonight, do this now.

As temporary risk reduction, disable Splunk Web if it is not required, and restrict access to Splunk Web to only necessary users. Limit low-privileged user ability to create or manipulate saved searches where operationally possible, and reduce exposure of higher-privileged users to untrusted saved search content until patches are applied. No specific detection signatures were provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to a fixed release: 9.4.4, 9.3.6, 9.2.8, or later. For Splunk Cloud Platform, fixed versions are 9.3.2411.108, 9.3.2408.118, 9.2.2406.123, or later; Splunk states that cloud patches are being applied automatically. Apply the vendor-provided security updates rather than relying solely on operational workarounds.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.