CVE-2024-6944
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 was found in ZhongBangKeJi CRMEB up to 5.4.0 and classified as critical. Affected by this issue is the function get_image_base64 of the file PublicController.php. The manipulation of the argument file leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-272066 is the identifier 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 confidenceA deserialization vulnerability exists in the get_image_base64 function of PublicController.php in ZhongBangKeJi CRMEB up to v5.4.0. Attackers can manipulate the 'file' argument to trigger unsafe deserialization, likely enabling remote code execution. The attack can be launched remotely and public exploits are 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<= 5.4.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify if CRMEB is installedLocate the CRMEB application installation directory and confirm the presence of the application files. Look for characteristic CRMEB directory structure and configuration files.Affected if CRMEB application is present in the environment
-
Determine the installed CRMEB versionCheck the version file or configuration within the CRMEB installation. Common locations include version.php, config files, or the admin panel version display. Compare the installed version against the affected range of <= 5.4.0.Affected if The installed version is 5.4.0 or lower
-
Locate the vulnerable PublicController.php fileFind the PublicController.php file within the application source code. This file should contain the get_image_base64 function that contains the deserialization vulnerability.Affected if The PublicController.php file exists and contains the get_image_base64 function
-
Verify the file parameter is accessibleIdentify the HTTP endpoint or route that calls the get_image_base64 function. Confirm that the 'file' parameter can be passed via GET or POST request to this endpoint.Affected if The endpoint accepting the file parameter is publicly accessible or accessible to untrusted users
-
Check for unsafe deserialization usageExamine the get_image_base64 function code to confirm it uses unserialize() or similar PHP deserialization functions on the file parameter without proper validation.Affected if The function performs deserialization on user-controlled input without validation
The environment is affected if CRMEB version 5.4.0 or lower is installed and the get_image_base64 function in PublicController.php accepts and deserializes the file parameter without validation.
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 dataUntil a vendor patch is available, implement strict input validation on the file parameter to restrict acceptable inputs, and apply network-level access controls to limit exposure. If possible, disable PHP unsafe deserialization functions or upgrade to a patched version.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6944 — 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-6944 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