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

中 5.4CVE-2025-48494 · GHSA-95rc-wc32-gm53 · GO-2025-3737 · 02/06/2025 公開 · 17/06/2026 更新

要点

CVE-2025-48494 は github.com/forceu/gokapi, gokapi (forceu) に影響する深刻度「中」 (CVSS 5.4) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.18%（全脆弱性の 7.3% より高い）。
対処：0.0.0-20250530191232-343cc566cfd7, 2.0.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/forceu/gokapi Go	`≥ 1.0.1, ≤ 1.9.6< 0.0.0-20250530191232-343cc566cfd7全バージョン`	`0.0.0-20250530191232-343cc566cfd7`
gokapi forceu	`= 2.0.0< 2.0.0`	`2.0.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.

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.