CVE-2026-33153: 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33153?
The severity of CVE-2026-33153 is classified as high due to the potential exposure of sensitive SQL queries.
How do I fix CVE-2026-33153?
To fix CVE-2026-33153, upgrade Tandoor Recipes to version 2.6.0 or later where the vulnerability has been addressed.
What data is leaked by CVE-2026-33153?
CVE-2026-33153 leaks full raw SQL queries, including database schema, table names, and access control logic.
Which versions of Tandoor Recipes are affected by CVE-2026-33153?
Tandoor Recipes versions prior to 2.6.0 are affected by CVE-2026-33153.
Is authentication required to exploit CVE-2026-33153?
No, CVE-2026-33153 can be exploited without authentication, making it more critical.