NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-48494: Gokapi vulnerable to stored XSS via uploading file with malicious file name

mediumCVSS 4.0 4.8GHSA-95rc-wc32-gm53

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.

Published Jun 3, 2025 · Updated Aug 26, 2025

Affected packages

github.com/forceu/gokapi

Ecosystem
Go
Affected
>= 1.0.1, <= 1.9.6
Fixed in
No patched version yet
Check
go list -m github.com/forceu/gokapi

github.com/forceu/gokapi

Ecosystem
Go
Affected
< 0.0.0-20250530191232-343cc566cfd7
Fixed in
0.0.0-20250530191232-343cc566cfd7
Check
go list -m github.com/forceu/gokapi

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to 4rdr, Forceu.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries