# CVE-2024-1750: TemmokuMVC Image Download images_get_down.php img_replace deserialization

> Remote attackers can exploit a deserialization flaw in the image download handler to potentially execute arbitrary code, though exploitation is difficult.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-4jff-4ww9-2jm5

## What is CVE-2024-1750?

CVE-2024-1750 is a medium-severity unsafe deserialization vulnerability in TemmokuMVC, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in TemmokuMVC up to 2.3. Affected is the function get_img_url/img_replace in the library lib/images_get_down.php of the component Image Download Handler. The manipulation leads to deserialization. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-254532. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Temmokumvc Temmokumvc.

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

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

## Is CVE-2024-1750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1750 is a medium-severity unsafe deserialization vulnerability in TemmokuMVC, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1750 in the wild and no public exploit code.

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

## Sources

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

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