dbcve.org
SplunkApplication

CVE-2023-40592

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-30
Fix available
A fix is available. Upgrade to 8.2.12 / 9.0.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.1.1, 9.0.6, and 8.2.12, an attacker can craft a special web request that can result in reflected cross-site scripting (XSS) on the “/app/search/table” web endpoint. Exploitation of this vulnerability can lead to the execution of arbitrary commands on the Splunk platform instance.

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 · moderate confidence

A reflected cross-site scripting (XSS) vulnerability exists in Splunk Enterprise versions below 9.1.1, 9.0.6, and 8.2.12 on the '/app/search/table' web endpoint. An attacker can craft a malicious web request containing JavaScript or HTML that gets reflected back to the user, allowing execution in the context of the victim's session. Successful exploitation can lead to arbitrary command execution on the Splunk platform instance.

MitigationUpgrade Splunk Enterprise to version 9.1.1, 9.0.6, or 8.2.12 or later to address this vulnerability.

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
SplunkApplication
Affected:>= 8.2.0, < 8.2.12>= 9.0.0, < 9.0.6= 9.1.0
Splunk Cloud PlatformApplication
Affected:<= 9.0.2305.100

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Splunk Enterprise version
    Run 'splunk --version' from the Splunk bin directory, or read the $SPLUNK_HOME/etc/splunk.version file, or log into the Splunk UI and navigate to Settings > About > Version
    Affected if The installed version is 8.2.0 through 8.2.11, 9.0.0 through 9.0.5, or exactly 9.1.0
  2. Confirm Splunk Web interface is enabled
    Check the web.conf configuration file located at $SPLUNK_HOME/etc/system/default/web.conf or $SPLUNK_HOME/etc/system/local/web.conf for the 'enableSplunkWeb' setting set to true
    Affected if Splunk Web is enabled (the web interface must be running for the /app/search/table endpoint to be accessible and exploitable)
  3. Verify access to the vulnerable endpoint
    Attempt to access the URL pattern 'https://<your-splunk-host>:<port>/en-US/app/search/table' using a web browser or curl command
    Affected if The endpoint responds with a page (the vulnerability requires this endpoint to be reachable, whether authenticated or not)

Your Splunk instance is affected if the installed version falls within 8.2.0-8.2.11, 9.0.0-9.0.5, or 9.1.0 AND Splunk Web is enabled and the /app/search/table endpoint is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 8.2.12 / 9.0.6 or later
Fixed in 8.2.129.0.6
Interim mitigation

Upgrade Splunk Enterprise to version 9.1.1, 9.0.6, or 8.2.12 or later to address this vulnerability.

Recommended fix High confidence

Splunk Enterprise: 8.2.12+ / 9.0.6+ / 9.1.1+ | Splunk Cloud: 9.0.2305.101+ (contact Splunk Support)

  1. 1. Identify your current Splunk Enterprise version using the About page or by running: splunk --version
  2. 2. For Splunk Enterprise 8.2.x: Upgrade to version 8.2.12 or later
  3. 3. For Splunk Enterprise 9.0.x: Upgrade to version 9.0.6 or later
  4. 4. For Splunk Enterprise 9.1.0: Upgrade to version 9.1.1 or later
  5. 5. For Splunk Cloud Platform: Contact Splunk Support to verify your environment has received the security patch (9.0.2305.101 or later)
  6. 6. After upgrade, verify the /app/search/endpoint is no longer vulnerable by testing with a benign payload or using Splunk's security scanning tools
Caveat Review Splunk Upgrade Guidelines for potential impacts to custom apps, configs, and integrations before upgrading

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

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40592 — 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-2023-40592 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