In breve
- CVE-2025-48494 è una vulnerabilità MEDIO (CVSS 5.4) che riguarda github.com/forceu/gokapi, gokapi (forceu).
- Probabilità di sfruttamento nei prossimi 30 giorni (EPSS): 0.18%, superiore al 7.3% delle vulnerabilità.
- Correzione: aggiornare a 0.0.0-20250530191232-343cc566cfd7, 2.0.0 o successiva.
| Package | Affected versions | Patched versions |
|---|
| github.com/forceu/gokapi Go | ≥ 1.0.1, ≤ 1.9.6< 0.0.0-20250530191232-343cc566cfd7all versions
| 0.0.0-20250530191232-343cc566cfd7
|
| gokapi | = 2.0.0< 2.0.0
| 2.0.0
|
Description
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.
NVD description
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 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. Prior to version 2.0.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 using a version prior to 2.0.0. If a user is the only authenticated user using Gokapi, they are not affected. This issue has been fixed in v2.0.0. A possible workaround would be to disable end-to-end encryption.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free