Gokapi vulnerable to stored XSS via uploading file with malicious file name
### Impact When using end-to-end encryption, a stored XSS vulnerability can be exploited by uploading a file with JavaScript code embedded in the filename. After upload and every time someone opens the upload list, the script is then parsed. With the affected versions <v2.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users with <v2.0. Nethertheless with XSS, other attack vectors like redirection or crypto mining would be possble. ### Patches This CVE has been fixed in v2.0.0 ### Workarounds If you are the only authenticated user using Gokapi, you are not affected. A workaround would be to disable end-to-end encryption.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-48494US | medium5.4 | — | ||
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. When using end-to-end encryption, a stored cross-site scripting vulnerability can be e… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/Forceu/GokapiPACKAGE
- https://github.com/Forceu/Gokapi/commit/343cc566cfd7f4efcd522c92371561d494aed6b0WEB
- https://github.com/Forceu/Gokapi/releases/tag/v2.0.0WEB
- https://github.com/Forceu/Gokapi/security/advisories/GHSA-95rc-wc32-gm53WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-48494ADVISORY
- https://pkg.go.dev/vuln/GO-2025-3737WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan