{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33153 exists.","fix":"No fix has been published for CVE-2026-33153 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33153 is a high-severity vulnerability in TandoorRecipes recipes, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33153 and fix it if it is affected.\n\nWhat it is: CVE-2026-33153 is a high-severity vulnerability in TandoorRecipes recipes, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33153 exists.\n\nAffected product: TandoorRecipes recipes. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33153/ (Markdown: https://insights.sbomify.com/CVE-2026-33153/index.md)","id":"CVE-2026-33153","markdown":"https://insights.sbomify.com/CVE-2026-33153/index.md","name":"CVE-2026-33153","record":{"aliases":["GHSA-f83r-v3h5-pchf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Recipe management app","requires_auth":"none","summary":"An unauthenticated debug parameter in Tandoor Recipes leaks raw SQL queries, exposing database schema and access control logic to any authenticated user.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"recipes","vendor":"tandoor"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in recipes","id":"CVE-2026-33153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver","id":"CVE-2026-33154"},"packages":[],"prev":{"headline":"Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication","id":"CVE-2026-33152"},"products":["recipes"],"published":"2026-03-26","related":[{"cvss_score":10,"headline":"Tandoor Recipes - SSTI - Remote Code Execution","id":"CVE-2025-23211","kev_date_added":null,"published":"2025-01-28"},{"cvss_score":9.1,"headline":"Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication","id":"CVE-2026-33152","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.7,"headline":"Tandoor Recipes - Stored XSS through Unrestricted File Upload","id":"CVE-2025-23213","kev_date_added":null,"published":"2025-01-28"},{"cvss_score":8.1,"headline":"Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users","id":"CVE-2026-35488","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":8.1,"headline":"Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification","id":"CVE-2026-35045","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.1,"headline":"Tandoor Recipes Vulnerable to Host Header Injection","id":"CVE-2026-33149","kev_date_added":null,"published":"2026-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["TandoorRecipes"]},"summary":"An unauthenticated debug parameter in Tandoor Recipes leaks raw SQL queries, exposing database schema and access control logic to any authenticated user.","url":"https://insights.sbomify.com/CVE-2026-33153/"}