CVE-2025-23213
Tandoor Recipes ≤ 1.5.28
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2025-23213 is a high-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Tandoor Recipes. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-23213 affects Tandoor Recipes, a self-hosted web application for managing recipes, planning meals, and building shopping lists. The vulnerability resides in the file upload feature, which permits the upload of arbitrary files, including HTML and SVG formats. These file types can embed malicious content such as XSS payloads, classified under CWE-434 (Unrestricted Upload of File with Dangerous Type). The issue has a CVSS v3.1 base score of 8.7 (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) and was fixed in version 1.5.28.
An authenticated user with low privileges can exploit this vulnerability over the network with low complexity by uploading a malicious HTML or SVG file containing XSS payloads. Exploitation requires user interaction, such as a victim viewing or interacting with the uploaded file. Successful attacks leverage the changed scope to achieve high confidentiality and integrity impacts, potentially allowing attackers to steal sensitive data like session cookies, perform actions on behalf of the victim, or escalate control within the application.
The Tandoor Recipes security advisory (GHSA-56jp-j3x5-hh2w) and the fixing commit (3e37d11c6a3841a00eb27670d1d003f1a713e1cf) confirm the vulnerability's resolution in version 1.5.28. Security practitioners should urge users to update to this version or later to mitigate the risk, and review file upload configurations to restrict dangerous MIME types like HTML and SVG in affected deployments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3145
Vulnerability Data
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. The file upload feature allows to upload arbitrary files, including html and svg. Both can contain malicious content (XSS Payloads). This vulnerability is fixed in 1.5.28.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.