Persistent XSS via unvalidated dashboard URL
Published Jul 1, 2024 · Updated Feb 28, 2025
Persistent XSS in Splunk Enterprise and Splunk Cloud Platform allows remote authenticated users to execute JavaScript in another user's browser. The Dashboard element accepts an invalid url parameter in a View without rejecting the URL and stores the resulting script-bearing payload. A low-privileged account without admin or power role access must create the View, and another user must open it for the script to run in that user's browser.
Summary
What happened
Persistent XSS in Splunk Enterprise and Splunk Cloud Platform allows remote authenticated users to execute JavaScript in another user's browser. The Dashboard element accepts an invalid url parameter in a View without rejecting the URL and stores the resulting script-bearing payload. A low-privileged account without admin or power role access must create the View, and another user must open it for the script to run in that user's browser.
The record
- CVE
- CVE-2024-36992
- Published
- Jul 1, 2024
- Updated
- Feb 28, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.0 <9.0.10
- Affected versionversion=9.1 <9.1.5
- Affected versionversion=9.2 <9.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo