We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-48495

Gokapi has stored XSS vulnerability in friendly name for API keys



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.

Reserved 2025-05-22 | Published 2025-06-02 | Updated 2025-06-02 | Assigner GitHub_M


MEDIUM: 4.8CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L

Problem types

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CWE-87: Improper Neutralization of Alternate XSS Syntax

Product status

< 2.0.0
affected

References

github.com/...Gokapi/security/advisories/GHSA-4xg4-54hm-9j77

github.com/...ommit/65ddbc68fbfdf1c80cadb477f4bcbb7f2c4fdbf8

cve.org (CVE-2025-48495)

nvd.nist.gov (CVE-2025-48495)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-48495

Support options

Helpdesk Chat, Email, Knowledgebase