Gokapi vulnerable to Privilege Escalation in File Replace
Published 13 Mar 2026 · Updated 24 Mar 2026
Is your project on an affected github.com/forceu/gokapi?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <2.2.4
- Fixed in
- 2.2.4
go get github.com/forceu/gokapi@v2.2.4Details
Summary
An insufficient authorization check in the file replace API allows a user with only list visibility permission (UserPermListOtherUploads) to delete another user's file by abusing the deleteNewFile flag, bypassing the requirement for UserPermDeleteOtherUploads.
Impact
Any authenticated user with PERM_REPLACE (replace own files) and PERM_LIST (view other users' uploads) can delete any other user's file without needing PERM_DELETE.
Is GHSA-j6jp-78w8-34x6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/forceu/gokapi, and gives you the command that fixes it.
More advisories for github.com/forceu/gokapi
- LowCVE-2026-30961Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload in github.com/forceu/gokapi · 16 Mar 2026
- LowCVE-2026-30955Gokapi vulnerable to DoS in E2E Metadata Parser in github.com/forceu/gokapi · 16 Mar 2026
- MediumCVE-2026-30961Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload · 13 Mar 2026
- MediumCVE-2026-30955Gokapi vulnerable to DoS in E2E Metadata Parser · 13 Mar 2026
- LowCVE-2026-28683Gokapi has Stored XSS in SVG Hotlinks in github.com/forceu/gokapi · 10 Mar 2026
- LowCVE-2026-28682Gokapi has Data Leak in Upload Status Stream in github.com/forceu/gokapi · 10 Mar 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.