CVE-2024-0603
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 classified as critical has been found in ZhiCms up to 4.0. This affects an unknown part of the file app/plug/controller/giftcontroller.php. The manipulation of the argument mylike leads to deserialization. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-250839.
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 confidenceZhiCms up to version 4.0 contains an insecure deserialization vulnerability in app/plug/controller/giftcontroller.php. The 'mylike' parameter is passed to PHP's unserialize() function without proper sanitization, allowing remote attackers to inject malicious serialized objects and achieve remote code execution. This is a critical unauthenticated RCE vulnerability.
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<= 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
- 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 ZhiCms installationLook for typical ZhiCms file structure - check for index.php or known ZhiCms directories in the web rootAffected if ZhiCms files are present on the server
-
Identify ZhiCms versionSearch for version information in source files, configuration, or version.php files - common locations include a version constant in index.php or a separate version fileAffected if Version is 4.0 or lower (or version cannot be determined but ZhiCms is present)
-
Locate vulnerable fileCheck if app/plug/controller/giftcontroller.php exists in the web application directoryAffected if The file giftcontroller.php exists in the expected path
-
Verify vulnerable unserialize callOpen giftcontroller.php and search for the 'mylike' parameter being passed to unserialize() function without sanitizationAffected if The code shows 'mylike' parameter directly fed to unserialize() without validation
-
Check if parameter is reachableReview the controller's function handling the 'mylike' parameter and determine if it can be accessed via HTTP request without authenticationAffected if The vulnerable parameter can be accessed remotely without authentication
If ZhiCms version 4.0 or lower is installed AND the file app/plug/controller/giftcontroller.php exists with the insecure unserialize() call on the 'mylike' parameter, the environment is affected by CVE-2024-0603.
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 dataUpgrade to a patched version of ZhiCms. If no upgrade is available, disable the affected giftcontroller.php or implement input validation to reject untrusted serialized data on the 'mylike' parameter.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0603 — 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-0603 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