# CVE-2024-31993: Mealie vulnerable to a GET-based SSRF in recipe image importer (GHSL-2023-227)

> Attackers can exploit unvalidated URL imports to perform Server-Side Request Forgery, potentially reading internal files or bypassing network restrictions.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-31993?

CVE-2024-31993 is a medium-severity server-side request forgery vulnerability in mealie-recipes mealie, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mealie is a self hosted recipe manager and meal planner. Prior to 1.4.0, the scrape_image function will retrieve an image based on a user-provided URL, however the provided URL is not validated to point to an external location and does not have any enforced rate limiting. The response from the Mealie server will also vary depending on whether or not the target file is an image, is not an image, or does not exist. Additionally, when a file is retrieved the file may remain stored on Mealie’s file system as original.jpg under the UUID of the recipe it was requested for. If the attacker has access to an admin account (e.g. the default changeme@example.com), this file can then be retrieved. Note that if Mealie is running in a development setting this could be leveraged by an attacker to retrieve any file that the Mealie server had downloaded in this fashion without the need for administrator access. This vulnerability is fixed in 1.4.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-31993?

It affects 1 product.


Products: Mealie Mealie.

## How do I fix CVE-2024-31993?

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

## Is CVE-2024-31993 being exploited?

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

## Other vulnerabilities in mealie-recipes mealie

- [CVE-2022-34615](https://insights.sbomify.com/CVE-2022-34615/): Weak cryptography in n/a (critical 9.8)
- [CVE-2025-56795](https://insights.sbomify.com/CVE-2025-56795/): Cross-site scripting in n/a (critical 9.0)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31993 and fix it if it is affected.

What it is: CVE-2024-31993 is a medium-severity server-side request forgery vulnerability in mealie-recipes mealie, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31993 exists.

Affected product: mealie-recipes mealie. 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-2024-31993/ (Markdown: https://insights.sbomify.com/CVE-2024-31993/index.md)
```

## Sources

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

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