Recipes CVE-2026-33153

Tandoor Recipes versions prior to 2.6.0. Attacker must be any authenticated user. Access the Recipe API endpoint with ?debug=true query parameter to expose raw SQL queries, table/column names, and multi-tenant space IDs regardless of Django DEBUG setting.

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) indicates network-accessible exploitation with low complexity and no user interaction, though the description clarifies authentication is actually required despite PR:N in the vector. SSVC framework confirms proof-of-concept exploit code exists and rates the vulnerability as automatable with partial technical impact, elevating practical risk. While not in CISA KEV (no active exploitation confirmed), the combination of POC availability, automatable exploitation, and information disclosure enabling follow-on attacks represents genuine risk for multi-tenant deployments. The high confidentiality impact (VC:H) is accurate as database schema exposure can facilitate privilege escalation, data exfiltration, or SQL injection attacks by revealing internal security controls. Real-world priority is moderate-to-high for organizations running affected versions, particularly in shared hosting or SaaS scenarios where tenant isolation depends on the exposed access control logic.

An authenticated attacker with low-privilege access to a Tandoor Recipes instance appends '?debug=true' to Recipe API endpoint requests, extracting complete SQL queries that reveal the database schema, tenant isolation column names (space IDs), and WHERE clause logic implementing access controls. Using this intelligence, the attacker maps relationships between users, recipes, and tenants, then crafts targeted SQL injection attacks or exploits logical flaws in the multi-tenant isolation to access recipes and data belonging to other users or organizations. Publicly available exploit code exists, and the attack requires only basic HTTP client tools with no complex exploitation techniques.