CVE-2025-20321 [Medium] | CSRF in Splunk

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-03	0.03%	0.07%	+0.04%
2	2025-07-08	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-03

0.03%

0.07%

+0.04%

2025-07-08

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	3.6	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

3.6

[email protected]

4.3

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

Affected software / configurations for CVE-2025-20321

Vendor	Product	Version	Raw CPE
splunk	splunk	>= 9.1.0, < 9.1.10	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.2.0, < 9.2.7	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.3.0, < 9.3.5	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.4.0, < 9.4.3	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk_cloud_platform	>= 9.2.2406, < 9.2.2406.119	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 9.3.2408, < 9.3.2408.114	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 9.3.2411, < 9.3.2411.104	cpe:2.3:a:splunk:splunk_cloud_platform::::::::

References for CVE-2025-20321

URL	Tags
https://advisory.splunk.com/advisories/SVD-2025-0704	Vendor Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2025-20321

Common vulnerability scoring system (CVSS) metrics for CVE-2025-20321

Weakness enumeration for CVE-2025-20321

Affected software / configurations for CVE-2025-20321

References for CVE-2025-20321