Skip to main content
CVE-2025-48495VulnerabilityPublished

CVE-2025-48495: Forceu Gokapi · Cross-site Scripting

Affects Forceu GokapiSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.0.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade forceu/Gokapi to 2.0.0.

Affected software

ProductAffectedFixed in
GitHubforceu/Gokapipkg:github/forceu/GokapiOther threatsAffected
  • <2.0.0
Fixed in
  • 2.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade to Gokapi version 2.0.0 or later, which includes fixes for this vulnerability through input sanitization and the introduction of a user permission system. 2. If immediate upgrade is not feasible, restrict access to the API key management page to trusted users only and avoid opening the API tab if there is suspicion of malicious code injection. 3. Implement network-level access controls and monitoring to detect anomalous behavior from authenticated users. 4. Enforce strong authentication mechanisms and monitor user activity logs for signs of abuse or unauthorized access. 5. Educate users about the risks of interacting with untrusted content within the application. 6. Consider deploying web application firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the API key overview page. 7. Regularly audit and rotate encryption keys and API keys to limit exposure in case of compromise. These steps go beyond generic advice by focusing on the specific context of Gokapi’s architecture and the vulnerability’s exploitation vector.

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.

References

Community reviews

Loading reviews…