CVE-2026-50890
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 · uneditedBernd Bestel grocy v4.6.0 was discovered to contain a SQL injection vulnerability in the product-group parameter at /stockreports/spendings. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.
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 confidenceA SQL injection vulnerability in grocy v4.6.0 allows remote attackers to inject malicious SQL code through the product-group parameter at the /stockreports/spendings endpoint, potentially exposing sensitive database information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify grocy installation versionLocate the grocy installation and check its version. Common methods: check package.json, composer.json, or the application's internal version file (often in /data or /config). If running as a container, check the image tag. For docker deployments, run 'docker images' and inspect labels.Affected if version is 4.6.0 or falls within an unpatched range and cannot be determined (unknown version)
-
Verify /stockreports/spendings endpoint accessibilityConfirm the endpoint is reachable in your environment. Check web server routing configuration (nginx/apache), reverse proxy settings, or firewall rules that expose this path. Verify authentication requirements for this route.Affected if the /stockreports/spendings endpoint is accessible to untrusted users or without proper authentication controls
-
Confirm product-group parameter processingReview application logs or code to identify how the product-group parameter is handled at the /stockreports/spendings endpoint. Check if raw parameter values are passed to SQL queries without parameterized query implementation.Affected if the product-group parameter is processed through direct string concatenation into SQL queries rather than using parameterized queries
-
Check for existing input validationInspect the application's input validation layer for the stockreports module. Look for sanitization, allowlist validation, or web application firewall rules targeting the product-group parameter.Affected if no input validation, sanitization, or compensating controls exist for the product-group parameter at this endpoint
You are affected if your grocy version is 4.6.0 or unpatched, the /stockreports/spendings endpoint is exposed, and the product-group parameter accepts unsanitized input that gets passed to SQL queries.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patch or upgrade to a fixed version; as a compensating control, implement parameterized queries and input validation on the product-group parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-50890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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