CrmebApplication

CVE-2024-6943

HIGH · 8.8 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to after 5.4.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in ZhongBangKeJi CRMEB up to 5.4.0 and classified as critical. Affected by this vulnerability is the function downloadImage of the file app/services/product/product/CopyTaobaoServices.php. The manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-272065 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

A PHP deserialization vulnerability exists in the downloadImage function of CopyTaobaoServices.php in ZhongBangKeJi CRMEB up to version 5.4.0. The function processes external input (likely image URLs or data) and passes it to PHP's unserialize() without proper validation, allowing remote attackers to inject malicious serialized objects and achieve code execution.

MitigationReplace unsafe unserialize() calls with secure alternatives like json_decode() and implement strict input validation on all data passed to deserialization functions. If the product copy feature is not actively used, consider disabling or removing the CopyTaobaoServices component until a patch is available.

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
CrmebApplication
Affected:<= 5.4.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CRMEB version
    Locate the version file or check the version constant in the application. Look for version.php in the application root or config directory, or check the admin panel system information page.
    Affected if Installed version is 5.4.0 or lower
  2. Find CopyTaobaoServices.php file
    Search the web root directory for the file CopyTaobaoServices.php, typically located in the application directory under a services or controller subfolder.
    Affected if The file exists in the application installation
  3. Verify copy/import feature is accessible
    Check if the product copy feature is enabled in the admin panel or accessible via URL. This feature processes the external input that reaches the vulnerable function.
    Affected if The copy feature is enabled or accessible to users
  4. Inspect vulnerable downloadImage function
    Open CopyTaobaoServices.php and locate the downloadImage function. Examine whether it contains unserialize() calls that process external input without proper validation.
    Affected if The function contains unserialize() handling user-supplied data

Environment is affected if running CRMEB version 5.4.0 or lower with the CopyTaobaoServices.php file present and the copy feature enabled or accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.4.0
Interim mitigation

Replace unsafe unserialize() calls with secure alternatives like json_decode() and implement strict input validation on all data passed to deserialization functions. If the product copy feature is not actively used, consider disabling or removing the CopyTaobaoServices component until a patch is available.

Fix this in Crmeb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6943 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6943 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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