CVE-2026-29084
CSRF Vulnerability in Gokapi Login Allows Unauthorized Access
Publication date: 2026-03-06
Last updated on: 2026-03-09
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| forceu | gokapi | to 2.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves the login endpoint accepting credential-bearing requests without CSRF protection. Detection can focus on monitoring login requests that lack CSRF tokens or originate from unexpected sources.'}, {'type': 'paragraph', 'content': 'You can inspect HTTP requests to the login endpoint for missing or invalid CSRF tokens. Network traffic analysis tools like Wireshark or command-line tools such as curl or tcpdump can be used to capture and analyze these requests.'}, {'type': 'list_item', 'content': "Use curl to simulate login requests and check for CSRF token requirements: curl -v -X POST https://your-gokapi-server/login -d 'username=USER&password=PASS'"}, {'type': 'list_item', 'content': "Use tcpdump to capture HTTP POST requests to the login endpoint: tcpdump -i any -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)'"}, {'type': 'list_item', 'content': 'Review server logs for login attempts that do not include CSRF tokens or originate from suspicious sources.'}] [1]
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-29084 is a Cross-Site Request Forgery (CSRF) vulnerability in the login endpoint of the Gokapi file sharing server, affecting versions prior to 2.2.3.'}, {'type': 'paragraph', 'content': 'The login flow accepts credential-bearing requests without implementing CSRF protection mechanisms tied to the browser session context. This means the login handler directly parses form values and creates a session upon successful credential validation without verifying if the request actually originated from the legitimate user.'}, {'type': 'paragraph', 'content': "An attacker can exploit this flaw by tricking a victim's browser into initiating a session linked to an attacker-controlled user account, where the attacker knows the credentials."}, {'type': 'paragraph', 'content': 'This can cause user confusion, misattribution of user activities, and potential misuse of trusted user actions.'}, {'type': 'paragraph', 'content': 'The vulnerability has been fixed in version 2.2.3 of Gokapi.'}] [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to coerce your browser into creating a session linked to an attacker-controlled account without your explicit consent.
As a result, you may experience confusion due to misattributed user activities, where actions performed during the session may be incorrectly associated with you.
There is also a risk of potential misuse of trusted user actions, which could affect the integrity of your interactions with the Gokapi server.
The confidentiality and integrity impacts are considered low, and there is no impact on service availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation is to upgrade Gokapi to version 2.2.3 or later, where the CSRF protection in the login flow has been implemented.
Until the upgrade can be applied, consider implementing additional CSRF protections at the web server or application firewall level, such as validating the Origin or Referer headers on login requests.
Also, monitor login activity for unusual patterns that might indicate exploitation attempts and educate users about the risks of interacting with untrusted sites while logged in.