# CVE-2024-31991: Mealie vulnerable to a GET-based SSRF in recipe importer (GHSL-2023-225)

> Authenticated users can exploit a Server-Side Request Forgery flaw to map internal HTTP servers on the local network via the recipe importer.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-31991?

CVE-2024-31991 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 safe_scrape_html function utilizes a user-controlled URL to issue a request to a remote server. Based on the content of the response, it will either parse the content or disregard it. This function, nor those that call it, add any restrictions on the URL that can be provided, nor is it restricted to being an FQDN (i.e., an IP address can be provided). As this function’s return will be handled differently by its caller depending on the response, it is possible for an attacker to use this functionality to positively identify HTTP(s) servers on the local network with any IP/port combination. This issue can result in any authenticated user being able to map HTTP servers on a local network that the Mealie service has access to. Note that by default any user can create an account on a Mealie server, and that the default changeme@example.com user is available with its hard-coded password. This vulnerability is fixed in 1.4.0.

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

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

It affects 1 product.


Products: Mealie Mealie.

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

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

## Is CVE-2024-31991 being exploited?

There is no known exploitation of CVE-2024-31991 in the wild and no public exploit code.

## 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-31991 and fix it if it is affected.

What it is: CVE-2024-31991 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: There is no known exploitation of CVE-2024-31991 in the wild and no public exploit code.

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-31991/ (Markdown: https://insights.sbomify.com/CVE-2024-31991/index.md)
```

## Sources

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

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