CVE-2025-48495: medium-severity vulnerability in Forceu Gokapi
Gokapi has stored XSS vulnerability in friendly name for API keys
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.8epss 0.1%
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.
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
Affected products
Forceu · GokapiRelated CVEs — Forceu Gokapi
In the same product, most dangerous first.
CVE-2026-30961MEDIUMGokapi's File Request MaxSize Limit Bypassed via Multi-Chunk UploadEPSS 0.3%CVE-2026-30955MEDIUMGokapi vulnerable to DoS in E2E Metadata ParserEPSS 0.3%CVE-2026-28683HIGHGokapi: Stored XSS in SVG HotlinksEPSS 0.2%CVE-2026-30943MEDIUMGokapi has Privilege Escalation in File ReplaceEPSS 0.2%CVE-2025-48494MEDIUMGokapi vulnerable to stored XSS via uploading file with malicious file nameEPSS 0.2%CVE-2026-29060MEDIUMGokapi: Privilege escalation with auth tokenEPSS 0.1%