CVE-2025-48495: Gokapi has stored XSS vulnerability in friendly name for API keys
Impact 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. With the affected versions <v2.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…
Published Jun 3, 2025 · Updated Aug 26, 2025
Affected packages
github.com/forceu/gokapi
- Ecosystem
- Go
- Affected
- >= 1.0.1, <= 1.9.6
- Fixed in
- No patched version yet
- Check
go list -m github.com/forceu/gokapi
github.com/forceu/gokapi
- Ecosystem
- Go
- Affected
- < 0.0.0-20250530185940-65ddbc68fbfd
- Fixed in
- 0.0.0-20250530185940-65ddbc68fbfd
- Check
go list -m github.com/forceu/gokapi
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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. With the affected versions <v2.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 with <v2.0. Nethertheless with XSS, other attack vectors like redirection or crypto mining would be possble.
Patches
This CVE has been fixed in v2.0.0
Workarounds
If you are the only authenticated user using Gokapi, you are not affected. A workaround would be to not open the API page if you suspect that another user might have injected code.
Credited to Forceu.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-30943
Gokapi vulnerable to Privilege Escalation in File Replace
medium4.1Mar 13, 2026CVE-2026-30955
Gokapi vulnerable to DoS in E2E Metadata Parser
medium6.5Mar 13, 2026CVE-2026-30961
Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload
medium4.3Mar 13, 2026CVE-2026-28682
Gokapi has Data Leak in Upload Status Stream
medium6.4Mar 5, 2026CVE-2026-28683
Gokapi has Stored XSS in SVG Hotlinks
high8.7Mar 5, 2026CVE-2026-29060
Gokapi has privilege escalation with auth token
medium5.0Mar 5, 2026
