CVE-2025-53833
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-53833 is a critical-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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.
LaRecipe is a documentation tool that renders Markdown content inside Laravel applications. Versions prior to 2.8.1 contain a Server-Side Template Injection vulnerability (CWE-1336) that can result in remote code execution when the application is deployed with certain template or configuration settings enabled. The flaw received a CVSS 3.1 score of 10.0, reflecting network-accessible, unauthenticated attack paths with high impact on confidentiality, integrity, and availability.
An unauthenticated remote attacker can supply crafted Markdown input that is processed by the template engine, allowing execution of arbitrary commands on the underlying server, disclosure of environment variables, or further privilege escalation depending on the runtime configuration. Because the vector requires no user interaction or credentials, any publicly reachable LaRecipe instance prior to the fix is exposed.
The project’s GitHub security advisory and associated pull request direct users to upgrade immediately to version 2.8.1 or later, where the injection issue has been addressed through the commit that sanitizes template input. The referenced advisory (GHSA-jv7x-xhv2-p5v2) and patch commit provide the concrete remediation steps.
EPSS for the CVE reached a peak of 0.3215 on 2026-02-18 before receding to the current value of 0.2082, indicating a period of elevated exploitation interest after disclosure. No information on observed in-the-wild exploitation is supplied in the available references.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21400
Vulnerability Data
LaRecipe is an application that allows users to create documentation with Markdown inside a Laravel app. Versions prior to 2.8.1 are vulnerable to Server-Side Template Injection (SSTI), which could potentially lead to Remote Code Execution (RCE) in vulnerable configurations. Attackers…
more
could execute arbitrary commands on the server, access sensitive environment variables, and/or escalate access depending on server configuration. Users are strongly advised to upgrade to version v2.8.1 or later to receive a patch.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2V1.3.7V1.3.10
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing neutralization of template directives.
Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.
Security engineering principles require use of safe templating APIs and proper escaping of external input.
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.
Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.
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.
Security testing can detect template-injection flaws but does not itself implement neutralization controls.
Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.
Application security requirements explicitly call for neutralizing special elements in template engines.
Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.
Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.