CVE-2024-31993 [Medium] | Security Vulnerability in Mealie

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 [email protected]), 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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.05%	0.41%	+0.35%
2	2025-09-08	0.03%	0.05%	+0.03%
3	2025-05-28	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.05%

0.41%

+0.35%

2025-09-08

0.03%

0.05%

+0.03%

2025-05-28

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.2	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.7	4.0	[email protected]
4.5	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	0.9	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.2

3.1

MEDIUM

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

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.7

4.0

[email protected]

4.5

3.1

MEDIUM

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

0.9

3.6

[email protected]

Affected software / configurations for CVE-2024-31993

Vendor	Product	Version	Raw CPE
mealie	mealie	< 1.4.0	cpe:2.3:a:mealie:mealie::::::::

References for CVE-2024-31993

URL	Tags
https://github.com/mealie-recipes/mealie/blob/ee121a12f8db33ecb4db5f8582f7ea9788d019e4/mealie/services/recipe/recipe_data_service.py#L107	Product
https://github.com/mealie-recipes/mealie/commit/2a3463b7466bc297aede50046da9550d919ec56f	Patch
https://github.com/mealie-recipes/mealie/pull/3368	Issue Tracking
https://securitylab.github.com/advisories/GHSL-2023-225_GHSL-2023-226_Mealie/	Third Party Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2024-31993

Common vulnerability scoring system (CVSS) metrics for CVE-2024-31993

Weakness enumeration for CVE-2024-31993

Affected software / configurations for CVE-2024-31993

References for CVE-2024-31993