Gokapi has CSRF in Login Endpoint
Published 5 Mar 2026 · Updated 23 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.3
- Fixed in
- 2.2.3
go get github.com/forceu/gokapi@v2.2.3Details
Summary
The login flow accepts credential-bearing requests without CSRF protection mechanisms tied to the browser session context. The handler parses form values directly and creates a session on successful credential validation.
*Issue found by [aisafe.io](aisafe.io)*
Impact
An attacker can force a victim browser into a session associated with an existing user account where the attacker knows the credentials, causing user confusion, activity misattribution, and potential misuse of trusted user actions.
Is GHSA-hcff-qv74-7hr4 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-30943Gokapi vulnerable to Privilege Escalation in File Replace 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
- MediumCVE-2026-30943Gokapi vulnerable to Privilege Escalation in File Replace · 13 Mar 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.