CVE Tools

CVE-2025-53833

LaRecipe is vulnerable to Server-Side Template Injection attacks

Exploitation likely. EPSS gives it a 9.1% chance of exploitation in the next 30 days. Fixed in 2.8.1.

Published Updated Sources: CVE.org, NVD, GitHub

What to do

Find your product and version, then upgrade to the build on the right.

  • Saleem-hadad LarecipeAffected: < 2.8.1Upgrade to: not statedStated by: CVE record
  • Packagist binarytorch/larecipeAffected: < 2.8.1Upgrade to: 2.8.1Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of LaRecipe (binarytorch/larecipe) your documentation site is running.
  2. If it's older than 2.8.1, treat it as vulnerable and plan an immediate update.
  3. Upgrade to binarytorch/larecipe version 2.8.1 or later.
  4. After upgrading, restart the application and verify the documentation pages still render correctly.
  5. If you can't upgrade immediately, restrict public access to the LaRecipe documentation pages until you can.
composer require binarytorch/larecipe:^2.8.1

What it is

From the CVE record

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.

In plain language

Written by AI from the record

If you use LaRecipe (a Laravel documentation tool) before version 2.8.1, attackers can take over your server without a password — update to 2.8.1 now.

LaRecipe <2.8.1 is vulnerable to unauthenticated Server-Side Template Injection (CWE-1336) in its Markdown documentation rendering, allowing arbitrary command execution, environment variable disclosure, and privilege escalation on the hosting server.

If you're affected

  • Full server takeover
  • Theft of secrets/credentials
  • Operational disruption
  • Privilege escalation on server

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS95th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

9.1% chance of exploitation activity in the next 30 days, which ranks it in the 95th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 458 days, from the signal feeds we watch.

  1. EPSS band changemoderate → lowepss band change
  2. EPSS band changelow → moderate
  3. EPSS band changelow → moderateepss band change
  4. EPSS band changemoderate → low
  5. Nuclei check added
  6. Patch availablerecord updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Larecipe, not every advisory.