Gokapi vulnerable to stored XSS via uploading file with malicious file name

TRUNG BÌNH 5.4CVE-2025-48494 · GHSA-95rc-wc32-gm53 · GO-2025-3737 · Công bố 02/06/2025 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2025-48494 là lỗ hổng mức TRUNG BÌNH (CVSS 5.4) ảnh hưởng github.com/forceu/gokapi, gokapi (forceu).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.18%, cao hơn 7.3% các lỗ hổng khác.
Cách xử lý: cập nhật lên 0.0.0-20250530191232-343cc566cfd7, 2.0.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/forceu/gokapi Go	`≥ 1.0.1, ≤ 1.9.6< 0.0.0-20250530191232-343cc566cfd7mọi phiên bản`	`0.0.0-20250530191232-343cc566cfd7`
gokapi forceu	`= 2.0.0< 2.0.0`	`2.0.0`

Mô tả

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.

Mô tả của NVD

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.