# CVE-2022-43561: Persistent Cross-Site Scripting in “Save Table” Dialog in Splunk Enterprise

> A remote user with the power role can inject persistent scripts via the Save Table dialog, enabling XSS attacks against other users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-8267-g4r9-6r3v

## What is CVE-2022-43561?

CVE-2022-43561 is a medium-severity cross-site scripting vulnerability in Splunk Splunk, published on 3 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2, a remote user that holds the “power” Splunk role can store arbitrary scripts that can lead to persistent cross-site scripting (XSS). The vulnerability affects instances with Splunk Web enabled.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-43561?

It affects 2 products.


Products: Splunk Splunk, Splunk Splunk Cloud Platform.

## How do I fix CVE-2022-43561?

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

## Is CVE-2022-43561 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43561 exists.

## 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-2022-43561 and fix it if it is affected.

What it is: CVE-2022-43561 is a medium-severity cross-site scripting vulnerability in Splunk Splunk, published on 3 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43561 exists.

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-2022-43561/ (Markdown: https://insights.sbomify.com/CVE-2022-43561/index.md)
```

## Sources

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

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