dbcve.org
RecipesApplication · Tandoor

CVE-2026-28503

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. In versions prior to 2.6.0, the `SyncViewSet.query_synced_folder()` action in `cookbook/views/api.py` (line 903) fetches a Sync object using `get_object_or_404(Sync, pk=pk)` without including `space=request.space` in the filter. This allows an admin user in Space A to trigger sync operations (Dropbox/Nextcloud/Local import) on Sync configurations belonging to Space B, and view the resulting sync logs. Version 2.6.0 patches the issue.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Tandoor Recipes application. The `SyncViewSet.query_synced_folder()` endpoint fetches a Sync object by primary key without validating that the object belongs to the user's Space, allowing any admin user to access and manipulate sync configurations (Dropbox/Nextcloud/Local) belonging to other Spaces.

MitigationUpgrade to Tandoor Recipes version 2.6.0 or later, which patches the issue by including `space=request.space` in the filter when fetching Sync objects.

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
RecipesApplication
Affected:< 2.6.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 Tandoor Recipes installation
    Locate the Tandoor Recipes application instance in your environment. This is a Django-based web application. Check your deployed applications list or container images.
    Affected if Tandoor Recipes is not deployed in your environment, this CVE does not apply.
  2. Determine installed version
    Access the admin interface or settings page to view the application version, or check the version file/codebase if you have direct access to the installation.
    Affected if The installed version is 2.6.0 or later; the vulnerability is patched. Versions below 2.6.0 are affected.
  3. Check if sync feature is configured
    Inspect the sync configurations in the application. Look for configured sync integrations (Dropbox, Nextcloud, or Local sync folders) in the Sync model/data.
    Affected if No sync configurations exist, the IDOR has no object to reference and the vulnerability cannot be exploited.
  4. Verify multiple Spaces exist
    Check if the application has multiple Spaces configured. This vulnerability allows cross-Space access to sync configurations, so multiple Spaces must exist for exploitation to have meaning.
    Affected if Only a single Space exists, exploitation has limited impact as there are no other Spaces to access.

You are affected if you are running Tandoor Recipes version below 2.6.0, have the sync feature enabled with configurations present, and operate in a multi-Space environment.

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 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Upgrade to Tandoor Recipes version 2.6.0 or later, which patches the issue by including `space=request.space` in the filter when fetching Sync objects.

Recommended fix High confidence

2.6.0

  1. Upgrade Tandoor Recipes to version 2.6.0 or later

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

Fix this in Recipes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28503 — 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-2026-28503 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