S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Jul 16, 2025

CVE-2025-53833 Scanner

Targets the Markdown rendering endpoint in LaRecipe, allowing an attacker to inject malicious template expressions and achieve remote code execution.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.3k
Times Used
continuous scan runs
6k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-53833
10.0
CVSScritical
Exploitable remotely over the internet · no authentication required.

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 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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
larecipeby saleem-hadad
< 2.8.1
Updated Sep 9, 2026View on NVD →
Detail

LaRecipe is a documentation creation application commonly used by developers and organizations for creating and managing technical documentation within Laravel applications. It employs Markdown for ease and flexibility. Integral to development environments, LaRecipe allows teams to maintain consistent documentation practices, ensuring information is up-to-date and accessible. The software is utilized globally by developers seeking a streamlined, integrated documentation solution within their Laravel framework. By offering a simple setup and an intuitive interface, LaRecipe enhances documentation workflow and improves team collaboration. This application is a pivotal component of many development teams' toolkits, emphasizing its widespread use and importance.

Server Side Template Injection (SSTI) is a critical vulnerability that allows an attacker to inject and execute code on the server through web application templates. This vulnerability arises when user inputs are concatenated into web application templates without sufficient validation or sanitization. As a result, attackers can inject malicious template expressions that the server executes, leading to remote code execution. In the context of LaRecipe, the vulnerability is present in the Markdown rendering functionality, where user-supplied content is processed without proper escaping.

The specific vulnerable endpoint is the documentation rendering route, where Markdown content is passed to the Blade template engine. The parameter 'content' or similar input fields are not sanitized before being rendered, allowing an attacker to inject Blade template syntax such as {{7*7}} or more complex expressions. This injection occurs because LaRecipe directly passes user input to the template engine without using the appropriate escaping functions, enabling the execution of arbitrary code on the server.

If exploited, an attacker can achieve full remote code execution on the server, potentially gaining complete control over the application and underlying system. This could lead to data breaches, unauthorized access to sensitive information, and further compromise of the infrastructure. Given the CVSS score of 10.0, this vulnerability is considered critical and requires immediate attention to prevent severe security incidents.

Solution Advice
  • Upgrade LaRecipe to version 2.8.1 or later, which includes a patch for the SSTI vulnerability.
  • Implement strict input validation and sanitization for all user-supplied content, especially Markdown inputs.
  • Use Laravel's built-in escaping functions like e() or Blade's {{ }} syntax with proper escaping to prevent template injection.
  • Disable or restrict the use of raw Blade directives in user-facing documentation features.
  • Conduct regular security audits and penetration testing to identify and remediate similar vulnerabilities.
  • Employ a Web Application Firewall (WAF) with rules to detect and block SSTI payloads.
  • Ensure server configurations follow the principle of least privilege to limit the impact of a successful exploit.
  • Monitor application logs for unusual template rendering errors or suspicious input patterns.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

LaRecipe SSTI Scanner | CVE-2025-53833 Free Check | S4E