Security Resilience

CVE-2024-55076

CSRF in Grocy Project Grocy ≤ 4.3.0

Public PoCCSRF
Published
06 January 2025
Modified
05 September 2025
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0032 24th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-55076 is a high-severity CSRF (CWE-352) vulnerability in Grocy Project Grocy. Its CVSS base score is 8.1 (High).

Operationally, ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-55076 is a Cross-Site Request Forgery (CSRF) vulnerability, mapped to CWE-352, affecting Grocy through version 4.3.0. This open-source self-hosted grocery and household management application lacks CSRF protection entirely, enabling unauthorized actions on behalf of authenticated users. The issue is demonstrated by an attacker's ability to change the administrator's password via a forged request.

The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating exploitation by unauthenticated attackers over the network, though it requires high attack complexity. Attackers can trick logged-in users into submitting malicious requests—such as via a crafted webpage or link—forcing actions like password changes without the user's knowledge or consent. This leads to high impacts on confidentiality, integrity, and availability, potentially allowing full administrative account takeover and subsequent control over the Grocy instance.

Advisories detail the vulnerability in the context of multiple issues in Grocy, including stored XSS and broken access control, as documented at https://m10x.de/posts/2024/11/all-your-recipe-are-belong-to-us-part-1/3-stored-xss-csrf-and-broken-access-control-vulnerabilities-in-grocy/. Security practitioners should consult this reference for exploitation proofs and recommended mitigations, such as upgrading to a patched version beyond 4.3.0 if available.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Grocy through 4.3.0 has no CSRF protection, as demonstrated by changing the Administrator's password.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-42270Same product: Grocy Project Grocy
CVE-2024-13560Shared CWE-352
CVE-2025-31921Shared CWE-352
CVE-2025-31457Shared CWE-352
CVE-2023-34033Shared CWE-352
CVE-2024-2960Shared CWE-352
CVE-2024-35009Shared CWE-352
CVE-2024-6136Shared CWE-352
CVE-2024-12003Shared CWE-352
CVE-2024-37431Shared CWE-352

Affected Assets

grocy project
grocy
≤ 4.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

References