CVE-2024-0603 is a high severity deserialization flaw in ZhiCms, scored CVSS 7.3. The record lists ZhiCms up to 4.0. The record names no fixed version. The sections below cover how to check and what to do first. The sections below cover how to check and what to do first.
What's affected
The record lists ZhiCms up to 4.0. The affected file is app/plug/controller/giftcontroller.php and the argument is mylike.
The CVSS vector in the record is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, with a base score of 7.3 (High). KEV status: not listed in the record.
Fixed version: The record names no fixed version. Check the project for a newer release.
How to check if you're exposed
Find the installed version in the product admin area, its version file, or your deployment manifest, and compare it with the record. Review web server access logs for unexpected requests to the affected path, and check whether the admin or affected component is reachable from the internet.
What to do now
- Find every deployment of the affected product and its version.
- Apply the vendor fix if one exists. If the vendor has not responded, consider removing the product or placing it behind a web application firewall and an IP allow list.
- Block or monitor requests to the affected path, and review logs for earlier abuse.
- Restrict the admin area to a trusted network.
Why it matters
CWE-502 describes this class. Deserialization of untrusted data means the application rebuilds objects from input that an outsider can influence. Depending on which classes are available, that can lead to unexpected behaviour or code execution. Avoid deserializing untrusted input, and prefer plain data formats such as JSON where possible.
The record notes that an exploit has been disclosed publicly, which shortens the time between disclosure and scanning by others. The record does not say the flaw is exploited in the wild, and it is not in the CISA KEV catalog.
For a wider view, a free in-browser dependency scan and the Gold directory show where ZhiCms sits in your software, and reachability analysis helps separate code that can actually be hit from code that merely ships.
Quick check
Is CVE-2024-0603 exploited in the wild?
The record's KEV flag is false, and none of the pages I fetched said otherwise. That is not proof of safety, so still patch or restrict access.
What if no fix exists?
Restrict the affected path and the admin area to trusted networks, and consider replacing the product.
Sources
- Safeguard Gold entry for CVE-2024-0603
- NVD record data for CVE-2024-0603, including the references listed there (the other reference pages were not fetched for this post).
Last reviewed: 19 October 2026.
