# CVE-2024-0739: Hecheng Leadshop leadshop.php deserialization

> Remote attackers can exploit unsafe deserialization in Leadshop to execute arbitrary code, requiring immediate patching.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/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:** 19 Jan 2024
- **Updated:** 21 Oct 2024
- **Also known as:** GHSA-h7fx-h2xw-6jjc

## What is CVE-2024-0739?

CVE-2024-0739 is a high-severity unsafe deserialization vulnerability in Hecheng Leadshop, published on 19 Jan 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 Hecheng Leadshop up to 1.4.20. Affected is an unknown function of the file /web/leadshop.php. The manipulation of the argument install leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-251562 is the identifier assigned to this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Leadshop Leadshop.

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

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

## Is CVE-2024-0739 being exploited?

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

## Other vulnerabilities in Hecheng Leadshop

- [CVE-2022-4136](https://insights.sbomify.com/CVE-2022-4136/): Exposed Dangerous Method or Function in qmpaas/leadshop (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0739 is a high-severity unsafe deserialization vulnerability in Hecheng Leadshop, published on 19 Jan 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-0739 in the wild and no public exploit code.

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

## Sources

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

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