dbcve.org
SplunkApplication

CVE-2024-36992

MEDIUM · 5.4 CVSS v3.1 Developing Published 2024-07-01
Fix available
A fix is available. Upgrade to 9.0.10 / 9.1.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.200 and 9.1.2308.207, a low-privileged user that does not hold the admin or power Splunk roles could craft a malicious payload through a View that could result in execution of unauthorized JavaScript code in the browser of a user. The “url” parameter of the Dashboard element does not have proper input validation to reject invalid URLs, which could lead to a Persistent Cross-site Scripting (XSS) exploit.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-02.

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
SplunkApplication
Affected:>= 9.0.0, < 9.0.10>= 9.1.0, < 9.1.5>= 9.2.0, < 9.2.2
Splunk Cloud PlatformApplication
Affected:>= 9.1.2308, < 9.1.2308.207>= 9.1.2312, < 9.1.2312.200

CVSS 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

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 · scoped
Upgrade available Upgrade to 9.0.10 / 9.1.5 / 9.1.2308.207 or later
Fixed in 9.0.109.1.59.1.2308.207
Recommended fix High confidence

Splunk Enterprise: 9.0.10, 9.1.5, or 9.2.2 (depending on current major version); Splunk Cloud Platform: 9.1.2308.207 or 9.1.2312.200

  1. 1. Identify your Splunk deployment type (Splunk Enterprise or Splunk Cloud Platform) and current version via Splunk Web (Settings > Server settings > Server information) or CLI: splunk version
  2. 2. For Splunk Enterprise: Determine your current major version (9.0.x, 9.1.x, or 9.2.x) and download the appropriate upgrade package from splunk.com
  3. 3. For Splunk Enterprise 9.0.x: Upgrade to version 9.0.10 or later
  4. 4. For Splunk Enterprise 9.1.x: Upgrade to version 9.1.5 or later
  5. 5. For Splunk Enterprise 9.2.x: Upgrade to version 9.2.2 or later
  6. 6. For Splunk Cloud Platform: Contact Splunk Support to request the security update for versions 9.1.2308.x (upgrade to 9.1.2308.207) or 9.1.2312.x (upgrade to 9.1.2312.200)
  7. 7. After upgrading, verify the fix by checking Splunk Enterprise version information confirms the patched version is running
  8. 8. Test that the Dashboard element properly validates the url parameter and rejects invalid/script-injected URLs
Caveat Splunk minor version upgrades typically preserve configurations, but review release notes for any behavior changes affecting custom views or dashboards

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36992 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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