CVE-2025-48494: Forceu Gokapi · Cross-site Scripting
Affects Forceu GokapiSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.0.0 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% 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:LExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
Upgrade forceu/Gokapi to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubforceu/Gokapipkg:github/forceu/GokapiOther threats | Affected
| Fixed in
|
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 immediately, as this version fixes the vulnerability and introduces user permission controls. 2. If upgrading is not immediately possible, disable end-to-end encryption as a temporary workaround to mitigate the XSS attack vector. 3. Implement strict input validation and output encoding on all user-supplied data, especially filenames, to prevent script injection. 4. Restrict authentication to trusted users only and monitor for unusual activity that could indicate exploitation attempts. 5. Educate users to be cautious when interacting with file lists and uploaded content, especially if unexpected behavior is observed. 6. Employ Content Security Policy (CSP) headers to limit the impact of any injected scripts. 7. Regularly audit and review user permissions and encryption key management to minimize exposure. 8. Monitor vendor advisories and threat intelligence feeds for any emerging exploit attempts or patches.
Description
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. When using end-to-end encryption, a stored cross-site scripting vulnerability can be exploited by uploading a file with JavaScript code embedded in the filename. After upload and every time someone opens the upload list, the script is then parsed. 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 using a version 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 possible workaround would be to disable end-to-end encryption.