CVE-2026-35489: CWE-639: Authorization Bypass Through User-Controlled Key in TandoorRecipes recipes
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the POST /api/food/{id}/shopping/ endpoint reads amount and unit directly from request.data and passes them without validation to ShoppingListEntry.objects.create(). Invalid amount values (non-numeric strings) cause an unhandled exception and HTTP 500. A unit ID from a different Space can be associated cross-space, leaking foreign-key references across tenant boundaries. All other endpoints creating ShoppingListEntry use ShoppingListEntrySerializer, which validates and sanitizes these fields. This vulnerability is fixed in 2.6.4.
AI Analysis
Technical Summary
Tandoor Recipes versions before 2.6.4 have an authorization bypass vulnerability (CWE-639) in the POST /api/food/{id}/shopping/ endpoint. This endpoint reads 'amount' and 'unit' directly from request data without validation and passes them to ShoppingListEntry.objects.create(), unlike other endpoints that use a serializer to validate and sanitize inputs. This leads to two issues: unhandled exceptions when 'amount' is non-numeric, causing HTTP 500 errors, and the ability to associate a unit ID from a different tenant space, leaking foreign-key references across tenant boundaries. The vulnerability is addressed in version 2.6.4.
Potential Impact
An attacker can cause denial of service via unhandled exceptions (HTTP 500) by submitting invalid 'amount' values. More critically, they can bypass tenant boundaries by associating shopping list entries with unit IDs from other spaces, potentially leaking data across tenants. The CVSS score of 7.3 reflects high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Tandoor Recipes to version 2.6.4 or later, where this vulnerability is fixed. The vendor has addressed the issue by adding proper validation and sanitization of input fields in the affected endpoint. No other mitigations are indicated or necessary once the update is applied.
CVE-2026-35489: CWE-639: Authorization Bypass Through User-Controlled Key in TandoorRecipes recipes
Description
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the POST /api/food/{id}/shopping/ endpoint reads amount and unit directly from request.data and passes them without validation to ShoppingListEntry.objects.create(). Invalid amount values (non-numeric strings) cause an unhandled exception and HTTP 500. A unit ID from a different Space can be associated cross-space, leaking foreign-key references across tenant boundaries. All other endpoints creating ShoppingListEntry use ShoppingListEntrySerializer, which validates and sanitizes these fields. This vulnerability is fixed in 2.6.4.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Tandoor Recipes versions before 2.6.4 have an authorization bypass vulnerability (CWE-639) in the POST /api/food/{id}/shopping/ endpoint. This endpoint reads 'amount' and 'unit' directly from request data without validation and passes them to ShoppingListEntry.objects.create(), unlike other endpoints that use a serializer to validate and sanitize inputs. This leads to two issues: unhandled exceptions when 'amount' is non-numeric, causing HTTP 500 errors, and the ability to associate a unit ID from a different tenant space, leaking foreign-key references across tenant boundaries. The vulnerability is addressed in version 2.6.4.
Potential Impact
An attacker can cause denial of service via unhandled exceptions (HTTP 500) by submitting invalid 'amount' values. More critically, they can bypass tenant boundaries by associating shopping list entries with unit IDs from other spaces, potentially leaking data across tenants. The CVSS score of 7.3 reflects high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Tandoor Recipes to version 2.6.4 or later, where this vulnerability is fixed. The vendor has addressed the issue by adding proper validation and sanitization of input fields in the affected endpoint. No other mitigations are indicated or necessary once the update is applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-02T20:49:44.454Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d52344aaed68159a2ec60c
Added to database: 4/7/2026, 3:31:16 PM
Last enriched: 4/7/2026, 3:46:30 PM
Last updated: 4/8/2026, 12:47:51 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.