CVE-2025-20321

Membership State Change in Splunk Search Head Cluster through a Cross-Site Request Forgery (CSRF) in Splunk Enterprise

MEDIUM

4.3

CVSS Score

Published: July 7, 2025 at 05:48 PM UTC

Updated: June 17, 2026 at 08:41 AM UTC

2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM4.3

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7 and 9.1.10, and Splunk Cloud Platform versions below 9.3.2411.104, 9.3.2408.114, and 9.2.2406.119, an unauthenticated attacker can send a specially-crafted SPL search that could change the membership state in a Splunk Search Head Cluster (SHC) through a Cross-Site Request Forgery (CSRF), potentially leading to the removal of the captain or a member of the SHC.<br><br>The vulnerability requires the attacker to phish the administrator-level victim by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Splunk · Splunk

95%

9.1 ≤ v < 9.1.109.1.0 ≤ v < 9.1.109.2 ≤ v < 9.2.79.2.0 ≤ v < 9.2.79.2.2406 ≤ v < 9.2.2406.1199.3 ≤ v < 9.3.59.3.0 ≤ v < 9.3.59.3.2408 ≤ v < 9.3.2408.1149.3.2411 ≤ v < 9.3.2411.1049.4 ≤ v < 9.4.39.4.0 ≤ v < 9.4.39.1 9.2 9.2.2406 9.3 9.3.2408 9.3.2411 9.4

Affected range stops below 9.1.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.2.2406.119, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.2.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.3.2408.114, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.3.2411.104, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.3.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.4.3, so it looks safe — our inference, not a vendor statement

Splunk Cloud Platform · Splunk

95%

9.2.2406 ≤ v < 9.2.2406.1199.3.2408 ≤ v < 9.3.2408.1149.3.2411 ≤ v < 9.3.2411.1049.2.2406 9.3.2408 9.3.2411

Affected range stops below 9.2.2406.119, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.3.2408.114, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.3.2411.104, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://advisory.splunk.com/advisories/SVD-2025-0704

References (1)

Vendor Advisory

Source: [email protected]

https://advisory.splunk.com/advisories/SVD-2025-0704

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: REQUIRED
Scope: UNCHANGED
Confidentiality: NONE
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card