# CVE-2024-45737: Maintenance mode state change of App Key Value Store (KVStore) through Cross-Site Request Forgery (CSRF)

> A low-privileged user can change the maintenance mode state of the App Key Value Store via CSRF, potentially disrupting operations or bypassing security controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2024
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-3pc3-p9j7-xvq6

## What is CVE-2024-45737?

CVE-2024-45737 is a medium-severity vulnerability in Splunk Splunk, published on 14 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk Enterprise versions below 9.3.1, 9.2.3, and 9.1.6 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).

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-45737?

It affects 2 products.


Products: Splunk Splunk, Splunk Splunk Cloud Platform.

## How do I fix CVE-2024-45737?

No fix has been published for CVE-2024-45737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45737 being exploited?

There is no known exploitation of CVE-2024-45737 in the wild and no public exploit code.

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45737 and fix it if it is affected.

What it is: CVE-2024-45737 is a medium-severity vulnerability in Splunk Splunk, published on 14 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45737 in the wild and no public exploit code.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45737/ (Markdown: https://insights.sbomify.com/CVE-2024-45737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45737
- OSV: https://osv.dev/vulnerability/CVE-2024-45737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45737/
Summaries are generated and may contain mistakes; the official description above is the record.
