# CVE-2022-46181: Gotify server XSS vulnerability in the application image file upload

> Authenticated users can upload HTML files to execute scripts when links are opened, potentially taking over victim accounts.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Dec 2022
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-xv6x-456v-24xh, GO-2022-1208

## What is CVE-2022-46181?

CVE-2022-46181 is a medium-severity cross-site scripting vulnerability in gotify server, published on 29 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Versions prior to 2.2.2 contain an XSS vulnerability that allows authenticated users to upload .html files. An attacker could execute client side scripts **if** another user opened a link. The attacker could potentially take over the account of the user that clicked the link. The Gotify UI won't natively expose such a malicious link, so an attacker has to get the user to open the malicious link in a context outside of Gotify. The vulnerability has been fixed in version 2.2.2. As a workaround, you can block access to non image files via a reverse proxy in the `./image` directory.

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

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

4 open source packages ship an affected version, including github.com/gotify/server and github.com/gotify/server/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gotify/server` | Go | All versions | None |
| `github.com/gotify/server` | Go | All versions | 2.2.2 |
| `github.com/gotify/server` | Go | All versions | 2.2.2 |
| `github.com/gotify/server/v2` | Go | All versions | 2.2.2 |

Products: Gotify Server.

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

Upgrade github.com/gotify/server to 2.2.2 or later.

## Is CVE-2022-46181 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46181 is a medium-severity cross-site scripting vulnerability in gotify server, published on 29 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-46181 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gotify/server (Go): affected all versions; no fix listed
- github.com/gotify/server (Go): affected all versions; fixed in 2.2.2
- github.com/gotify/server (Go): affected all versions; fixed in 2.2.2
- github.com/gotify/server/v2 (Go): affected all versions; fixed in 2.2.2

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

## Sources

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

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