Skip to main content
CVE-2025-56795VulnerabilityPublished Updated

CVE-2025-56795: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.0 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2025-56795, European organizations should take the following specific actions: 1) Monitor Mealie project channels for official patches and apply them promptly once released. 2) Implement strict input validation on the server side to sanitize and whitelist acceptable characters in the "note" and "text" fields before storage. 3) Apply proper output encoding/escaping in the frontend to neutralize any injected scripts when rendering user-generated content. 4) Restrict access to the "/api/recipes/{recipe_name}" endpoint to only trusted and necessary users, minimizing the attack surface. 5) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 6) Conduct regular security awareness training for users to recognize and report suspicious activity. 7) Use Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting this endpoint. 8) Audit user privileges and enforce the principle of least privilege to reduce the impact of compromised accounts. 9) Monitor logs for unusual API usage patterns or repeated failed attempts to inject scripts. 10) Consider isolating or sandboxing the application environment to contain potential exploitation effects.

Description

Mealie 3.0.1 and earlier is vulnerable to Stored Cross-Site Scripting (XSS) in the recipe creation functionality. Unsanitized user input in the "note" and "text" fields of the "/api/recipes/{recipe_name}" endpoint is rendered in the frontend without proper escaping leading to persistent XSS.

References

Community reviews

Loading reviews…