CVE-2024-0739
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA PHP deserialization vulnerability exists in Hecheng Leadshop up to v1.4.20 in the /web/leadshop.php file. The 'install' parameter is vulnerable to unsafe deserialization, potentially allowing remote attackers to execute arbitrary code by crafting malicious serialized objects.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.4.0, <= 1.4.20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Leadshop installation existsCheck for the presence of the Leadshop application on the server by searching for leadshop.php in the web root directory, or look for Leadshop-specific directories and files.Affected if The Leadshop application is present on the server.
-
Identify installed Leadshop versionExamine the /web/leadshop.php file for a version number, or look for a version file in the Leadshop installation directory. Compare the found version against the affected range of >= 1.4.0 and <= 1.4.20.Affected if The installed version falls within 1.4.0 to 1.4.20 inclusive.
-
Verify vulnerable file existsConfirm the presence of the file /web/leadshop.php in the web-accessible directory.Affected if The file /web/leadshop.php exists on the system.
-
Check if install parameter is accessibleReview the application's routing configuration and the leadshop.php file to determine if the 'install' parameter is processed and reachable via HTTP requests.Affected if The 'install' parameter is processed by the application without proper sanitization.
A user is affected if Leadshop is installed with a version between 1.4.0 and 1.4.20 inclusive, the /web/leadshop.php file exists, and the application processes the 'install' parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately upgrade to a patched version if available, or disable the vulnerable install functionality. Implement strict input validation on the 'install' parameter and consider deploying a WAF rule to block known deserialization attack patterns until a permanent fix is applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0739 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data