# CVE-2022-47968: Cross-site scripting in n/a

> Attackers can inject malicious scripts via application names, leading to code execution or account takeover in the Heimdall dashboard.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-9q9r-fmgh-vv5v

## What is CVE-2022-47968?

CVE-2022-47968 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Heimdall Application Dashboard through 2.5.4 allows reflected and stored XSS via "Application name" to the "Add application" page. The stored XSS will be triggered in the "Application list" page.

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

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

It affects 1 product.


Products: Linuxserver Heimdall Application Dashboard.

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

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

## Is CVE-2022-47968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-54597](https://insights.sbomify.com/CVE-2025-54597/): Cross-site scripting in Heimdall (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47968 and fix it if it is affected.

What it is: CVE-2022-47968 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Dec 2022. Any signed-in user can exploit it over the network, 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-47968 exists.

Affected product: n/a. 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-47968/ (Markdown: https://insights.sbomify.com/CVE-2022-47968/index.md)
```

## Sources

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

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