dbcve.org
GrocyApplication · Grocy Project

CVE-2023-48866

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-04
Fix available
A fix is available. Upgrade to after 4.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Cross-Site Scripting (XSS) vulnerability in the recipe preparation component within /api/objects/recipes and note component within /api/objects/shopping_lists/ of Grocy <= 4.0.3 allows attackers to obtain the victim's cookies.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in Grocy <= 4.0.3 affecting the recipe preparation component (/api/objects/recipes) and shopping list notes (/api/objects/shopping_lists/). Attackers can inject malicious scripts that execute when victims view the affected data, enabling cookie theft and session hijacking.

MitigationImplement proper input validation and output encoding/escaping for user-supplied content in recipe and shopping list endpoints. Upgrade to version > 4.0.3 if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrocyApplication
Affected:<= 4.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Grocy version
    Locate the Grocy installation and check the version number, typically found in a version file, changelog, or by querying the API endpoint that returns version info
    Affected if The installed version is 4.0.3 or lower (any version <= 4.0.3)
  2. Inspect recipe preparation data for suspicious content
    Query the recipes endpoint (/api/objects/recipes) or directly inspect the recipes table in the database for any HTML, JavaScript, or script tags in preparation-related fields
    Affected if Any recipe preparation content contains unencoded script tags, event handlers (onclick, onerror, etc.), or javascript: URIs
  3. Inspect shopping list notes for suspicious content
    Query the shopping lists endpoint (/api/objects/shopping_lists/) or directly inspect the shopping_lists table in the database for any HTML or script tags in notes fields
    Affected if Any shopping list note contains unencoded script tags, event handlers, or javascript: URIs
  4. Verify API responses lack output encoding
    Make an authenticated API request to /api/objects/recipes or /api/objects/shopping_lists/ and examine if user-supplied content is returned with HTML entities properly encoded (e.g., < becomes &lt;)
    Affected if User-supplied content in API responses is returned raw without HTML encoding

You are affected if your Grocy version is 4.0.3 or lower AND you have any recipe preparation or shopping list entries containing unsanitized script tags or HTML in your database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.0.3
Interim mitigation

Implement proper input validation and output encoding/escaping for user-supplied content in recipe and shopping list endpoints. Upgrade to version > 4.0.3 if available.

Recommended fix Moderate confidence

Grocy 4.0.4 or later stable release

  1. 1. Backup your Grocy installation and database before performing any upgrade.
  2. 2. Download the latest stable release of Grocy from the official GitHub repository (github.com/grocy/grocy).
  3. 3. Replace the existing Grocy files with the new version, preserving your configuration and data files.
  4. 4. Verify the upgrade by accessing the Grocy web interface.
  5. 5. Test the recipe preparation and shopping list note components to confirm the XSS vulnerability is remediated.
Caveat Minor version upgrade - review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grocy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48866 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data