CVE-2022-46181

gotify/server vulnerable to Cross-site Scripting in the application image file upload

Workarounds

You can block access to non image files via a reverse proxy in the ./image directory.

References

https://github.com/gotify/server/pull/534
https://github.com/gotify/server/pull/535

Thanks to rickshang (aka 无在无不在) for discovering and reporting this bug.

The XSS vulnerability allows authenticated users to upload .html files. With that, an attacker could execute client side scripts if another user opened a link, such as:

https://push.example.org/image/[alphanumeric string].html

An attacker could potentially take over the account of the user that clicked the link. Keep in mind, 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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-46181 has a CVSS score of 4.6 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The vulnerability has been fixed in version 2.2.2.

1. What is CVE-2022-46181? CVE-2022-46181 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/gotify/server (go), affecting versions <= 2.2.1. It is fixed in 2.2.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-46181? CVE-2022-46181 has a CVSS score of 4.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/gotify/server are affected by CVE-2022-46181? github.com/gotify/server (go) versions <= 2.2.1 is affected.
4. Is there a fix for CVE-2022-46181? Yes. CVE-2022-46181 is fixed in 2.2.2. Upgrade to this version or later.
5. Is CVE-2022-46181 exploitable, and should I be worried? Whether CVE-2022-46181 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-46181 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-46181? Upgrade github.com/gotify/server to 2.2.2 or later.

Other vulnerabilities in github.com/gotify/server