dbcve.org
SplunkApplication

CVE-2025-20228

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 9.1.8 / 9.1.2312.204 or later.
See remediation →
72/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.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.2.2403.108, and 9.1.2312.204, a low-privileged user that does not hold the "admin" or "power" Splunk roles could change the maintenance mode state of App Key Value Store (KVStore) through a Cross-Site Request Forgery (CSRF).

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in Splunk Enterprise and Cloud Platform where a low-privileged user without admin or power roles can change the maintenance mode state of the App Key Value Store (KVStore). The attacker would need to trick a victim into clicking a malicious link that triggers an authenticated request to the vulnerable endpoint.

MitigationUpgrade Splunk Enterprise to versions 9.3.3, 9.2.5, or 9.1.8 (or Splunk Cloud Platform to 9.2.2403.108 or 9.1.2312.204) to obtain the patch. As a CSRF fix, this typically involves adding anti-CSRF token validation to the affected KVStore maintenance mode endpoint.

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:>= 9.1.0, < 9.1.8>= 9.2.0, < 9.2.5>= 9.3.0, < 9.3.3
Splunk Cloud PlatformApplication
Affected:>= 9.1.2312, < 9.1.2312.204>= 9.2.2403.100, < 9.2.2403.107

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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. Identify installed Splunk Enterprise version
    Navigate to Settings > About > About Splunk or run the command: splunk --version or curl -k https://localhost:8089/services/server/info?output_mode=json
    Affected if The version falls within 9.1.0 to 9.1.7, 9.2.0 to 9.2.4, or 9.3.0 to 9.3.2 (for Splunk Enterprise)
  2. Identify installed Splunk Cloud Platform version
    Check the Cloud Portal for the deployed Splunk Cloud version or consult your cloud administration console
    Affected if The version falls within 9.1.2312 to 9.1.2312.203 or 9.2.2403.100 to 9.2.2403.106 (for Splunk Cloud Platform)
  3. Verify KVStore is in use
    Check if any apps or configurations rely on KVStore by searching for collections in Settings > Data > Collections, or run: | rest /servicesNS/-/system/storage/collections/config
    Affected if KVStore collections exist and the Splunk version is vulnerable
  4. Review audit logs for KVStore maintenance mode changes
    Search the _internal index for maintenance mode changes: index=_internal sourcetype=splunkd component=RestHandler endpoint=*kvstore*action=* OR search the audit index: index=_audit action=kvstore*
    Affected if Unexpected or unauthorized maintenance mode state changes appear in logs without corresponding legitimate admin actions

You are affected if your Splunk version is within the vulnerable ranges listed AND KVStore is enabled, as the CSRF flaw allows a low-privileged user to manipulate KVStore maintenance mode through a maliciously crafted link.

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 9.1.8 / 9.1.2312.204 / 9.2.5 or later
Fixed in 9.1.89.1.2312.2049.2.5
Interim mitigation

Upgrade Splunk Enterprise to versions 9.3.3, 9.2.5, or 9.1.8 (or Splunk Cloud Platform to 9.2.2403.108 or 9.1.2312.204) to obtain the patch. As a CSRF fix, this typically involves adding anti-CSRF token validation to the affected KVStore maintenance mode endpoint.

Recommended fix High confidence

Splunk Enterprise: 9.1.8, 9.2.5, or 9.3.3 (or later) | Splunk Cloud Platform: 9.1.2312.204 or 9.2.2403.108 (or later)

  1. Identify whether you are using Splunk Enterprise or Splunk Cloud Platform
  2. For Splunk Enterprise: Upgrade to version 9.1.8, 9.2.5, 9.3.3, or any later stable release that contains the fix
  3. For Splunk Cloud Platform: Contact Splunk Support to verify that your deployment has been upgraded to version 9.1.2312.204 or 9.2.2403.108 (or later)
  4. After upgrading, verify that the KVStore maintenance mode can only be changed by users with appropriate admin or power roles
Caveat Standard Splunk upgrade best practices apply - review Splunk upgrade documentation, test in non-production environment first, and ensure backup of configuration

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

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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