# CVE-2025-56795: Cross-site scripting in n/a

> Attackers can inject malicious scripts via recipe notes, leading to persistent XSS and potential account takeover in Mealie.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-wwm7-v4rv-ggff

## What is CVE-2025-56795?

CVE-2025-56795 is a critical cross-site scripting vulnerability in n/a, published on 29 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-56795?

It affects 1 product.


Products: Mealie Mealie.

## How do I fix CVE-2025-56795?

No fix has been published for CVE-2025-56795 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56795 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56795 exists.

Public exploit code:

- Stored Cross-Site Scripting (XSS) vulnerability affecting the recipe creation functionality in Mealie versions up to 3.0.1. (github_poc): https://github.com/B1tBreaker/CVE-2025-56795

## Other vulnerabilities in n/a

- [CVE-2022-34615](https://insights.sbomify.com/CVE-2022-34615/): Weak cryptography in n/a (critical 9.8)
- [CVE-2024-55073](https://insights.sbomify.com/CVE-2024-55073/): Missing authorization in n/a (high 7.6)
- [CVE-2024-31992](https://insights.sbomify.com/CVE-2024-31992/): Mealie contains a DoS vulnerability in recipe importer (medium 6.5)
- [CVE-2024-31994](https://insights.sbomify.com/CVE-2024-31994/): Mealie vulnerable to a DoS in recipe image importer (GHSL-2023-228) (medium 6.5)
- [CVE-2022-34621](https://insights.sbomify.com/CVE-2022-34621/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56795 and fix it if it is affected.

What it is: CVE-2025-56795 is a critical cross-site scripting vulnerability in n/a, published on 29 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56795 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-56795/ (Markdown: https://insights.sbomify.com/CVE-2025-56795/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-56795
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-56795
- OSV: https://osv.dev/vulnerability/CVE-2025-56795

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-56795/
Summaries are generated and may contain mistakes; the official description above is the record.