NVD / CVE Program· CNA Splunk

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

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.7 · v3.1—No exploit No fix recorded

Info leak

Published: Dec 10, 2024
Updated: Jun 17, 2026
EPSS: 0.4% · 40th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.7
CNA · Splunk: 5.7; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
splunk	splunk	cpe:2.3:a:splunk:splunk
splunk	splunk cloud platform	cpe:2.3:a:splunk:splunk_cloud_platform

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

splunk splunk9.1.0 and later · before 9.1.7
splunk splunk9.2.0 and later · before 9.2.4
splunk splunk9.3.0 and later · before 9.3.2
splunk splunk cloud platform9.1.2312 and later · before 9.1.2312.206
splunk splunk cloud platform9.2.2403 and later · before 9.2.2403.109
splunk splunk cloud platform9.2.2406 and later · before 9.2.2406.107

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Splunk). Independent of NVD's CPE analysis and usually ahead of it.

Splunk Splunk Cloud Platform
- 9.2.2406 and later · before 9.2.2406.107affected
- 9.2.2403 and later · before 9.2.2403.109affected
- 9.1.2312 and later · before 9.1.2312.206affected
Splunk Splunk Enterprise
- 9.3 and later · before 9.3.2affected
- 9.2 and later · before 9.2.4affected
- 9.1 and later · before 9.1.7affected

Same product

splunk: all records

Other highest-scoring records for the same primary product.

CVE-2026-20253Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk EnterpriseKEV
98Now
CVE-2018-11409Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as demon
60This week
CVE-2023-32707‘edit_user’ Capability Privilege Escalation
59Plan

Published before and after this one in the same product

← EarlierCVE-2024-45740Oct 14, 2024 · Persistent Cross-Site Scripting (XSS) through Scheduled Views on Splunk Enterprise
21Monitor
← EarlierCVE-2024-45741Oct 14, 2024 · Persistent Cross-Site Scripting (XSS) via props.conf on Splunk Enterprise
25Monitor
Later →CVE-2024-53245Dec 10, 2024 · Information Disclosure due to Username Collision with a Role that has the same Name as the User
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-20141435 days apartImproper Access Control in Splunk Monitoring Console App
26Monitor
CVE-2026-20164456 days apartSensitive Information Disclosure through Improper Access Control in Splunk Enterprise
26Monitor
CVE-2025-20226106 days apartRisky command safeguards bypass in “/services/streams/search“ endpoint through “q“ parameter in Splunk Enterprise
22Monitor
CVE-2025-20232106 days apartRisky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in Splunk Enterprise
22Monitor
CVE-2026-20137435 days apartRisky Commands Safeguards Bypass through preloaded Data Models due to Path Traversal vulnerability in Splunk Enterprise
22Monitor
CVE-2025-20325209 days apartSensitive Information Disclosure in the SHCConfig logging channel in Clustered Deployments in Splunk Enterprise
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

advisory.splunk.com/advisories/SVD-2024-1202

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records