CVE-2025-48495

Gokapi has stored XSS vulnerability in friendly name for API keys

Published Jun 2, 2025 CVSS 4.0 · 4.8 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-16636 Gokapi has stored XSS vulnerability in friendly name for API keys
Github GHSA Github GHSA GHSA-4xg4-54hm-9j77 Gokapi has stored XSS vulnerability in friendly name for API keys
History
Type Values Removed Values Added
CPEs cpe:2.3:a:forceu:gokapi:2.0.0:beta1:*:*:*:*:*:*
cpe:2.3:a:forceu:gokapi:2.0.0:beta2:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Forceu
Forceu gokapi
CPEs cpe:2.3:a:forceu:gokapi:*:*:*:*:*:*:*:*
Vendors & Products Forceu
Forceu gokapi
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Gokapi has stored XSS vulnerability in friendly name for API keys
Weaknesses CWE-79
CWE-87
References
Metrics cvssV4_0

{'score': 4.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jun 2, 2025, 4:51 PM
Reserved
May 22, 2025, 12:11 PM
Status
Analyzed
Published
Jun 2, 2025, 12:15 PM
Modified
Jun 17, 2026, 9:29 AM