CVE-2024-53244

Risky command safeguards bypass in “/en-US/app/search/report“ endpoint through “s“ parameter

MEDIUM
5.7
CVSS Score
Published: December 10, 2024 at 06:01 PM UTC
Updated: June 17, 2026 at 08:08 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
Severity
MEDIUM5.7
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In Splunk Enterprise versions below 9.3.2, 9.2.4, and 9.1.7 and Splunk Cloud Platform versions below 9.2.2406.107, 9.2.2403.109, and 9.1.2312.206, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on “/en-US/app/search/report“ endpoint through “s“ parameter.<br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user 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.

9.1 ≤ v < 9.1.79.1.0 ≤ v < 9.1.79.2 ≤ v < 9.2.49.2.0 ≤ v < 9.2.49.3 ≤ v < 9.3.29.3.0 ≤ v < 9.3.29.19.29.3
Affected range stops below 9.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2, so it looks safe — our inference, not a vendor statement
9.1.2312 ≤ v < 9.1.2312.2069.2.2403 ≤ v < 9.2.2403.1099.2.2406 ≤ v < 9.2.2406.1079.1.23129.2.24039.2.2406
Affected range stops below 9.1.2312.206, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.2403.109, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.2406.107, 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:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

5.7MEDIUMSplunk
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200NVD-CWE-noinfo

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.

Free plan, no card