Approved changes feed: RSS · Atom
cpe:2.3:a:tandoor:recipes:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tandoor (4502c384-284d-555d-99c1-ce0903ec51af) |
|---|---|
| Product | Recipes (eb2c29f5-1080-5cf2-abad-c5ab40e486a5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-35489 |
vulnerable | 2026-06-08 07:59:14.053102 |
Tandoor Recipes — `amount`/`unit` bypass serializer in `food/{id}/shopping/`
HIGH (7.3)
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.
Published: 2026-04-07T14:53:18.333Z
Updated: 2026-04-07T15:58:45.810Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35488 |
vulnerable | 2026-06-08 07:59:14.052700 |
Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users
HIGH (8.1)
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, RecipeBookViewSet and RecipeBookEntryViewSet use CustomIsShared as an alternative permission class, but CustomIsShared.has_object_permission() returns True for all HTTP methods — including DELETE, PUT, and PATCH — without checking request.method in SAFE_METHODS. Any user who is in the shared list of a RecipeBook can delete or overwrite it, even though shared access is semantically read-only. This vulnerability is fixed in 2.6.4.
Published: 2026-04-07T14:51:25.861Z
Updated: 2026-04-08T14:48:54.946Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35046 |
vulnerable | 2026-06-08 07:59:13.438116 |
Tandoor has a Stored CSS Injection via <style> Tag in Recipe Instructions (API-Level)
MEDIUM (5.4)
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, Tandoor Recipes allows authenticated users to inject arbitrary <style> tags into recipe step instructions. The bleach.clean() sanitizer explicitly whitelists the <style> tag, causing the backend to persist and serve unsanitized CSS payloads via the API. Any client consuming instructions_markdown from the API and rendering it as HTML without additional sanitization will execute attacker-controlled CSS — enabling UI redressing, phishing overlays, visual defacement, and CSS-based data exfiltration. This vulnerability is fixed in 2.6.4.
Published: 2026-04-06T17:20:00.579Z
Updated: 2026-04-07T15:59:42.719Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35045 |
vulnerable | 2026-06-08 07:59:13.437643 |
Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification
HIGH (8.1)
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the PUT /api/recipe/batch_update/ endpoint in Tandoor Recipes allows any authenticated user within a Space to modify any recipe in that Space, including recipes marked as private by other users. This bypasses all object-level authorization checks enforced on standard single-recipe endpoints (PUT /api/recipe/{id}/), enabling forced exposure of private recipes, unauthorized self-grant of access via the shared list, and metadata tampering. This vulnerability is fixed in 2.6.4.
Published: 2026-04-06T17:17:57.647Z
Updated: 2026-04-07T14:29:07.687Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33153 |
vulnerable | 2026-06-08 07:59:09.178357 |
Tandoor Recipes's Unauthenticated Debug Parameter Leaks Full Raw SQL Queries Including Schema, Table Names, and Access Control Logic
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. In versions prior to 2.6.0, the Recipe API endpoint exposes a hidden `?debug=true` query parameter that returns the complete raw SQL query being executed, including all table names, column names, JOIN relationships, WHERE conditions (revealing access control logic), and multi-tenant space IDs. This parameter works even when Django's `DEBUG=False` (production mode) and is accessible to any authenticated user regardless of their privilege level. This allows a low-privilege attacker to map the entire database schema and reverse-engineer the authorization model. Version 2.6.0 patches the issue.
Published: 2026-03-26T19:06:16.020Z
Updated: 2026-03-26T19:52:10.149Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33152 |
vulnerable | 2026-06-08 07:59:09.177727 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33149 |
vulnerable | 2026-06-08 07:59:09.163684 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33148 |
vulnerable | 2026-06-08 07:59:09.163168 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-29055 |
vulnerable | 2026-06-08 07:55:16.045460 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-28503 |
vulnerable | 2026-06-08 07:55:15.377887 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27460 |
vulnerable | 2026-06-08 07:53:22.341085 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25991 |
vulnerable | 2026-06-08 07:53:20.668673 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25964 |
vulnerable | 2026-06-08 07:53:20.652842 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-23213 |
vulnerable | 2026-06-08 07:10:55.354567 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-23212 |
vulnerable | 2026-06-08 07:10:55.354044 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-23211 |
vulnerable | 2026-06-08 07:10:55.353519 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23074 |
vulnerable | 2026-06-08 05:40:56.149113 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23073 |
vulnerable | 2026-06-08 05:40:56.148652 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23072 |
vulnerable | 2026-06-08 05:40:56.148293 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23071 |
vulnerable | 2026-06-08 05:40:56.147834 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.