GHSA-xv6x-456v-24xh
MEDIUMGHSA-xv6x-456v-24xh is a medium-severity (CVSS 4.6) Cross-site Scripting (XSS) vulnerability in github.com/gotify/server. O3 Security confirms whether GHSA-xv6x-456v-24xh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
gotify/server vulnerable to Cross-site Scripting in the application image file upload
Blast Radius
github.com/gotify/serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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.
Patches
The vulnerability has been fixed in version 2.2.2.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gotify/server | all versions | 2.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gotify/server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/gotify/server to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xv6x-456v-24xh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xv6x-456v-24xh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-xv6x-456v-24xh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xv6x-456v-24xh in your dependencies?
O3 detects GHSA-xv6x-456v-24xh across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.