# CVE-2025-23211: Tandoor Recipes - SSTI - Remote Code Execution

> An attacker can execute arbitrary commands on the server via a Jinja2 SSTI vulnerability in Tandoor Recipes.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2025
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-r6rj-h75w-vj8v

## What is CVE-2025-23211?

CVE-2025-23211 is a critical code injection vulnerability in TandoorRecipes recipes, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. A Jinja2 SSTI vulnerability allows any user to execute commands on the server. In the case of the provided Docker Compose file as root. This vulnerability is fixed in 1.5.24.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2025-23211?

It affects 1 product.


Products: Tandoor Recipes.

## How do I fix CVE-2025-23211?

No fix has been published for CVE-2025-23211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-23211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23211 exists.

Public exploit code:

- https://github.com/IIxoskeletonII/DataPrivacy-CVE-2025-23211 (github_poc): https://github.com/IIxoskeletonII/DataPrivacy-CVE-2025-23211
- Tandoor Recipes < 1.5.24 - Jinja2 SSTI RCE (nuclei): http/cves/2025/CVE-2025-23211.yaml

## Other vulnerabilities in TandoorRecipes recipes

- [CVE-2026-33152](https://insights.sbomify.com/CVE-2026-33152/): Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication (critical 9.1)
- [CVE-2025-23213](https://insights.sbomify.com/CVE-2025-23213/): Tandoor Recipes - Stored XSS through Unrestricted File Upload (high 8.7)
- [CVE-2026-35488](https://insights.sbomify.com/CVE-2026-35488/): Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users (high 8.1)
- [CVE-2026-35045](https://insights.sbomify.com/CVE-2026-35045/): Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification (high 8.1)
- [CVE-2026-33149](https://insights.sbomify.com/CVE-2026-33149/): Tandoor Recipes Vulnerable to Host Header Injection (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23211 and fix it if it is affected.

What it is: CVE-2025-23211 is a critical code injection vulnerability in TandoorRecipes recipes, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23211 exists.

Affected product: TandoorRecipes recipes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23211/ (Markdown: https://insights.sbomify.com/CVE-2025-23211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23211
- OSV: https://osv.dev/vulnerability/CVE-2025-23211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23211/
Summaries are generated and may contain mistakes; the official description above is the record.