CVE-2024-55075VulnerabilityPublished 6 Jan 2025

CVE-2024-55075: Grocy · Forced Browsing

Affects GrocySource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Grocy project Grocy	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-55075, organizations should implement strict access control policies to ensure that only authorized users can access sensitive endpoints, even if accessed directly via URL. This includes enforcing role-based access controls (RBAC) within Grocy and validating user permissions on the server side for all endpoints, not just those linked in the UI. Network segmentation and firewall rules can restrict access to Grocy instances to trusted internal networks or VPN users only. Monitoring and logging access to sensitive pages can help detect unauthorized attempts to exploit forced browsing. Until an official patch is released, consider disabling or restricting access to non-UI-exposed pages if feasible. Regularly update Grocy to the latest versions once patches addressing this vulnerability become available. Additionally, educate users about the risks of sharing credentials and enforce strong authentication mechanisms to reduce the likelihood of low-privilege account compromise.

Description

Grocy through 4.3.0 allows remote attackers to obtain sensitive information via direct requests to pages that are not shown in the UI, such as calendar and recipes.

Impact

The primary impact of CVE-2024-55075 is unauthorized disclosure of sensitive information stored within Grocy, such as calendar entries and recipe details. While this does not affect data integrity or system availability, the leakage of confidential information could lead to privacy violations or give attackers insights into user behavior and system usage. For organizations using Grocy in environments handling sensitive operational data—such as healthcare facilities managing medical supplies, hospitality businesses managing inventory, or supply chain operations—this information disclosure could facilitate further targeted attacks or social engineering. The requirement for low-level privileges reduces the risk somewhat but does not eliminate it, especially in environments where user accounts are shared or weakly controlled. The lack of known exploits and patches means organizations may be exposed until a fix is available, increasing the window of vulnerability.

CWE-425Direct Request ('Forced Browsing') (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
Architecture and Design · Operation
Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
Architecture and Design
Consider using MVC based frameworks such as Struts.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
Attack patterns
Directory Indexing (opens in a new tab)
Detect Unpublicized Web Pages (opens in a new tab)
Detect Unpublicized Web Services (opens in a new tab)
Key Negotiation of Bluetooth Attack (KNOB) (opens in a new tab)
Forceful Browsing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 02:00 UTC

WeaknessesCWE-425

Technical details

References

Community reviews

Related threats