CVE-2025-48495: Gokapi has stored XSS vulnerability in friendly name for API keys

Severity: medium (CVSS 5.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-06-02 · updated 2026-06-17
Weakness: CWE-79

Description

Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. By renaming the friendly name of an API key, an authenticated user could inject JS into the API key overview, which would also be executed when another user clicks on his API tab. 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 of versions 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 workaround would be to not open the API page if it is possible that another user might have injected code.

Affected products

Forceu Gokapi: before 2.0.0; 2.0.0-beta1, 2.0.0-beta2 — fixed in 2.0.0

How to fix

Upgrade to a fixed version: Forceu Gokapi 2.0.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-48495 or the next vulnerability affects your stack