CVE-2024-55076: Grocy · Cross-Site Request Forgery (CSRF)
Affects GrocySource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 4.3.1 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 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 Grocy to 4.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Grocy project Grocy | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2024-55076, organizations should immediately implement the following measures: 1) Restrict network access to Grocy instances by placing them behind firewalls or VPNs to limit exposure to untrusted networks. 2) Employ web application firewalls (WAFs) with rules designed to detect and block CSRF attack patterns. 4) Implement multi-factor authentication (MFA) for administrative accounts to reduce the impact of unauthorized password changes. 5) Regularly audit administrative account activities and monitor logs for suspicious password changes or access patterns. 6) Educate users about the risks of visiting untrusted websites while authenticated to Grocy, as CSRF attacks rely on the victim’s browser context. 7) Consider deploying custom CSRF tokens or other anti-CSRF mechanisms at the web server or reverse proxy level if upgrading is not immediately feasible. 8) Backup Grocy data regularly to enable recovery in case of compromise. These steps provide layered defense until an official patch is released.
Description
Grocy through 4.3.0 has no CSRF protection, as demonstrated by changing the Administrator's password.