CVE-2024-0987 is a medium severity log neutralization flaw flaw, scored 6.3, in KuERP up to 1.0.4. The public record names no fixed version and says the vendor did not respond. Restrict network access to the product, check your installed version against the one named in the record, and watch the vendor or project page for a patch.
What's affected
Affected: KuERP (Sichuan Yougou Technology) up to 1.0.4. The record's CVSS 3.1 score is 6.3 (medium), with vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The record names the file /runtime/log. The weakness is filed as CWE-117, CWE-116.
Fixed version: The record names no fixed version, and it notes that the vendor was contacted early and did not respond. No patched release is confirmed.
The record's kev flag is false, so this CVE is not in the CISA Known Exploited Vulnerabilities catalog. One thing to note: the VulDB wording in the description calls the issue critical, while the CVSS score in the record is 6.3, which is medium. Treat the numeric score and your own exposure as the guide, and know that both labels exist.
How to check if you're exposed
- Find the product in your inventory and confirm the version. Many of these small applications are installed from a source archive, so the version may live in a file or a database table and not in a package manager.
- Check which networks can reach the application, and whether it is exposed to the internet.
- Request the log path from outside the intended network and see whether it answers. Check your web server configuration for runtime or log directories that sit inside the public document root.
- Check the vendor or project page for a release newer than the affected one.
What to do now
- Take the product off the internet if it is exposed. Put it behind a VPN or an allow list of known addresses.
- Restrict access at the network layer to the people and systems that need it.
- Watch the vendor or project page for a fixed release, and apply it when one appears. The record says the vendor did not respond to disclosure, so do not wait on it: plan to replace the product if it handles sensitive data.
- Review logs for the signs above and rotate administrator credentials if you see anything unusual.
- Add the product to your inventory and monitoring so a future fix or advisory reaches you. A free in-browser dependency scan covers the third party packages in software you build, though it does not inspect device firmware.
Why it matters
Improper output neutralization for logs means data written to a log or served from a log location is not cleaned first. Depending on how logs are stored and read, that can let someone forge entries, hide activity or inject content into whatever tool later displays the log.
Log files are often trusted by the people reading them during an incident. If an outsider can shape what goes into them, or read them directly from a web path, the log stops being reliable evidence and can leak internal details.
Smaller commercial and sample code projects often have no security contact and no release cadence. If no fix arrives, the choices are to harden around the product or to replace it.
The record states that the exploit has been disclosed to the public. That means details are available to others, not that attacks have been observed. Only CISA KEV or a vendor advisory can say that, and neither does here.
Quick check
Is this CVE exploited in the wild?
The record's kev flag is false, so it is not in the CISA Known Exploited Vulnerabilities catalog, and no source I read reports active exploitation. The record does say a public exploit exists. That is a reason to patch or contain it soon, not a report of attacks.
What if there is no patch?
Reduce exposure. Remove internet access, restrict the network, apply the log and credential checks above, and plan to replace the product if it holds sensitive data.
Sources
- Safeguard Gold entry for CVE-2024-0987, built from the NVD record
- NVD record fields: description, CVSS 3.1 vector, CWE list and CPE product data. I did not fetch the researcher write ups listed in the record, so the details above are limited to what the record states.
Last reviewed: 19 October 2026.
