In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated user could later open a legacy investigation workbench that renders the panel. The script could then run in the browser of the user who opened the workbench and expose data or actions available through Splunk Web to the user who opened the workbench.
The vulnerability is possible because Splunk Enterprise Security does not escape legacy investigation workbench panel titles before rendering them in Splunk Web.
For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Review and finish existing legacy investigations in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/investigations/review-and-finish-existing-legacy-investigations-in-splunk-enterprise-security) in the Splunk documentation.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.


Workaround

Turn off or remove the Splunk Enterprise Security app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.

History

Thu, 19 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
Description In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated user could later open a legacy investigation workbench that renders the panel. The script could then run in the browser of the user who opened the workbench and expose data or actions available through Splunk Web to the user who opened the workbench. The vulnerability is possible because Splunk Enterprise Security does not escape legacy investigation workbench panel titles before rendering them in Splunk Web. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Review and finish existing legacy investigations in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/investigations/review-and-finish-existing-legacy-investigations-in-splunk-enterprise-security) in the Splunk documentation.
Title Stored Cross-Site Scripting (XSS) through Legacy Investigation Workbench Panel Titles in Splunk Enterprise Security
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-11-19T19:55:55.424Z

Reserved: 2026-11-17T20:26:14.303Z

Link: CVE-2026-131216

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-19T20:17:35.573

Modified: 2026-11-19T20:17:35.573

Link: CVE-2026-131216

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses