CVE-2024-45740
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 · uneditedIn Splunk Enterprise versions below 9.2.3 and 9.1.6 and Splunk Cloud Platform versions below 9.2.2403, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through Scheduled Views that 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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Splunk Enterprise and Cloud Platform where a low-privileged user (non-admin, non-power) can inject malicious JavaScript through Scheduled Views. The crafted payload executes in the browser of other users viewing those scheduled reports, leading to potential session hijacking or data theft.
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>= 9.1.0, < 9.1.6>= 9.2.0, < 9.2.3< 9.2.2403.100CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionNavigate to Settings > About > Version or run: splunk versionAffected if Version is >= 9.1.0 and < 9.1.6, or >= 9.2.0 and < 9.2.3
-
Check Splunk Cloud Platform versionNavigate to Splunk Cloud Portal or check the deployment info in the Cloud Platform settingsAffected if Version is < 9.2.2403.100
-
Identify if Scheduled Views feature is enabledGo to Settings > Visualization > Scheduled Reports or check the scheduledviews.conf configuration file in $SPLUNK_HOME/etc/system/local/Affected if Scheduled Views are enabled and accessible to low-privileged users
-
Review existing Scheduled Views for malicious payloadsGo to Settings > Searches, reports, and alerts > Scheduled Reports and inspect the View names and descriptions for suspicious script tags or JavaScript patternsAffected if Any scheduled view contains injected XSS payloads like <script> tags or event handlers
-
Check user role assignments for Scheduled View creationNavigate to Settings > Users and Authentication > Roles and verify which roles have the 'schedule_search' capability and can create viewsAffected if Non-admin, non-power users have permission to create or modify Scheduled Views
You are affected if your Splunk version falls within the vulnerable ranges AND Scheduled Views are accessible to low-privileged users, or if existing scheduled views contain suspicious XSS payloads.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1.69.2.39.2.2403.100
Upgrade Splunk Enterprise to versions 9.2.3, 9.1.6 or later, or Splunk Cloud Platform to 9.2.2403 or later. Alternatively, restrict or disable Scheduled Views for untrusted users until the patch can be applied.
Splunk Enterprise: upgrade to 9.1.6 or 9.2.3; Splunk Cloud Platform: upgrade to 9.2.2403.100 or later
- 1. Back up your Splunk environment including configuration files, apps, and any custom content before initiating the upgrade
- 2. Review Splunk's official upgrade documentation for your deployment type (single instance, distributed, or cloud)
- 3. For Splunk Enterprise: Download version 9.1.6 or 9.2.3 (depending on your current major version branch) from splunk.com
- 4. For Splunk Cloud Platform: Contact Splunk Support to schedule the upgrade to version 9.2.2403.100 or later
- 5. Test the upgrade in a non-production environment first to validate compatibility with your custom apps and configurations
- 6. Execute the upgrade following Splunk's standard upgrade procedures
- 7. After upgrade, verify the Scheduled Views functionality works correctly and the vulnerability is patched
- 8. Confirm the version by navigating to Settings > About > Version in the Splunk web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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