CVE-2026-33149: CWE-644: Improper Neutralization of HTTP Headers for Scripting Syntax in TandoorRecipes recipes
CVE-2026-33149 is a high-severity vulnerability in Tandoor Recipes (versions up to 2. 5. 3) caused by improper validation of the HTTP Host header due to ALLOWED_HOSTS being set to '*'. This allows attackers to craft malicious Host headers that manipulate server-generated absolute URLs, including invite links sent via email. The primary risk is invite link poisoning, where an attacker can redirect invite tokens to their own server, potentially gaining unauthorized access by using stolen tokens on the real application. Exploitation requires the attacker to send crafted requests and trick an admin into sending invites. The vulnerability impacts confidentiality and integrity but does not affect availability. No known exploits are currently reported, and no patch is confirmed available yet. Organizations using Tandoor Recipes should urgently review their configurations and monitor for suspicious invite activity.
AI Analysis
Technical Summary
CVE-2026-33149 affects Tandoor Recipes, an application for recipe management, meal planning, and shopping list creation. Versions up to and including 2.5.3 have a critical security flaw stemming from the Django framework setting ALLOWED_HOSTS to '*' by default, which disables validation of the HTTP Host header. This misconfiguration allows an attacker to supply arbitrary Host header values in HTTP requests. The application uses Django's request.build_absolute_uri() method to generate absolute URLs in various contexts such as invite link emails, API pagination, and OpenAPI schema generation. Because the Host header is not validated, these URLs can be manipulated to point to attacker-controlled domains. The most severe consequence is invite link poisoning: when an administrator creates an invite, the generated email contains a link with the attacker’s domain instead of the legitimate application URL. If the invitee clicks this link, the invite token is sent to the attacker, who can then use it to gain unauthorized access to the real application. This vulnerability is categorized under CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax), highlighting the failure to properly sanitize or validate HTTP headers. The CVSS 3.1 base score is 8.1 (high), reflecting network attack vector, low attack complexity, high privileges required, user interaction needed, and a scope change with high confidentiality and integrity impacts but no availability impact. No patches or fixes are currently documented, and no active exploits have been reported in the wild as of publication.
Potential Impact
The vulnerability primarily threatens the confidentiality and integrity of user data and application access controls. By poisoning invite links, attackers can intercept invite tokens, allowing them to impersonate legitimate users or gain unauthorized access to the application. This can lead to unauthorized data exposure, manipulation of user accounts, and potential lateral movement within an organization’s environment. Since the vulnerability affects the generation of absolute URLs used in emails and APIs, it can also undermine user trust and facilitate phishing or social engineering attacks. The attack requires an attacker to send crafted requests and rely on an administrator to send invites, which limits the attack surface but does not eliminate the risk in environments where invites are frequently used. Organizations relying on Tandoor Recipes for internal or external user management face significant risk of account compromise and data leakage if unmitigated. The lack of a patch increases exposure time, making timely mitigation critical.
Mitigation Recommendations
Organizations should immediately review and update the ALLOWED_HOSTS setting in their Tandoor Recipes deployment to explicitly list trusted hostnames instead of using '*'. This change enforces proper validation of the Host header and prevents arbitrary URL generation. Until a patch is available, administrators should avoid sending invite emails or disable invite functionality if feasible. Monitoring email logs and invite token usage for anomalies can help detect exploitation attempts. Implementing additional validation on invite tokens and restricting their usage by IP or time can reduce risk. Network-level protections such as Web Application Firewalls (WAFs) can be configured to block suspicious Host headers. Educating administrators about the risk of clicking unexpected invite links and verifying URLs before use is also important. Organizations should track vendor updates for official patches and apply them promptly once released. Finally, consider isolating the Tandoor Recipes application behind reverse proxies that enforce strict host header validation.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, Sweden, Japan, South Korea
CVE-2026-33149: CWE-644: Improper Neutralization of HTTP Headers for Scripting Syntax in TandoorRecipes recipes
Description
CVE-2026-33149 is a high-severity vulnerability in Tandoor Recipes (versions up to 2. 5. 3) caused by improper validation of the HTTP Host header due to ALLOWED_HOSTS being set to '*'. This allows attackers to craft malicious Host headers that manipulate server-generated absolute URLs, including invite links sent via email. The primary risk is invite link poisoning, where an attacker can redirect invite tokens to their own server, potentially gaining unauthorized access by using stolen tokens on the real application. Exploitation requires the attacker to send crafted requests and trick an admin into sending invites. The vulnerability impacts confidentiality and integrity but does not affect availability. No known exploits are currently reported, and no patch is confirmed available yet. Organizations using Tandoor Recipes should urgently review their configurations and monitor for suspicious invite activity.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33149 affects Tandoor Recipes, an application for recipe management, meal planning, and shopping list creation. Versions up to and including 2.5.3 have a critical security flaw stemming from the Django framework setting ALLOWED_HOSTS to '*' by default, which disables validation of the HTTP Host header. This misconfiguration allows an attacker to supply arbitrary Host header values in HTTP requests. The application uses Django's request.build_absolute_uri() method to generate absolute URLs in various contexts such as invite link emails, API pagination, and OpenAPI schema generation. Because the Host header is not validated, these URLs can be manipulated to point to attacker-controlled domains. The most severe consequence is invite link poisoning: when an administrator creates an invite, the generated email contains a link with the attacker’s domain instead of the legitimate application URL. If the invitee clicks this link, the invite token is sent to the attacker, who can then use it to gain unauthorized access to the real application. This vulnerability is categorized under CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax), highlighting the failure to properly sanitize or validate HTTP headers. The CVSS 3.1 base score is 8.1 (high), reflecting network attack vector, low attack complexity, high privileges required, user interaction needed, and a scope change with high confidentiality and integrity impacts but no availability impact. No patches or fixes are currently documented, and no active exploits have been reported in the wild as of publication.
Potential Impact
The vulnerability primarily threatens the confidentiality and integrity of user data and application access controls. By poisoning invite links, attackers can intercept invite tokens, allowing them to impersonate legitimate users or gain unauthorized access to the application. This can lead to unauthorized data exposure, manipulation of user accounts, and potential lateral movement within an organization’s environment. Since the vulnerability affects the generation of absolute URLs used in emails and APIs, it can also undermine user trust and facilitate phishing or social engineering attacks. The attack requires an attacker to send crafted requests and rely on an administrator to send invites, which limits the attack surface but does not eliminate the risk in environments where invites are frequently used. Organizations relying on Tandoor Recipes for internal or external user management face significant risk of account compromise and data leakage if unmitigated. The lack of a patch increases exposure time, making timely mitigation critical.
Mitigation Recommendations
Organizations should immediately review and update the ALLOWED_HOSTS setting in their Tandoor Recipes deployment to explicitly list trusted hostnames instead of using '*'. This change enforces proper validation of the Host header and prevents arbitrary URL generation. Until a patch is available, administrators should avoid sending invite emails or disable invite functionality if feasible. Monitoring email logs and invite token usage for anomalies can help detect exploitation attempts. Implementing additional validation on invite tokens and restricting their usage by IP or time can reduce risk. Network-level protections such as Web Application Firewalls (WAFs) can be configured to block suspicious Host headers. Educating administrators about the risk of clicking unexpected invite links and verifying URLs before use is also important. Organizations should track vendor updates for official patches and apply them promptly once released. Finally, consider isolating the Tandoor Recipes application behind reverse proxies that enforce strict host header validation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T21:17:08.885Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c589313c064ed76fb167ca
Added to database: 3/26/2026, 7:29:53 PM
Last enriched: 3/26/2026, 7:45:30 PM
Last updated: 3/26/2026, 9:06:19 PM
Views: 4
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.
External Links
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.