CVE-2024-32370: HSC Cybersecurity HC Mailinspector · Exposed IOCTL with Insufficient Access Control
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Immediately isolate affected HC Mailinspector instances from external networks to reduce exposure until a patch is available.
- Monitor network traffic for unusual requests targeting the mliSystemUsers.php component, especially those manipulating the id parameter.
- Implement strict input validation and web application firewall (WAF) rules to block suspicious payloads aimed at the vulnerable parameter.
- Restrict access to the HC Mailinspector management interfaces to trusted IP addresses and require strong authentication mechanisms.
- Regularly check for vendor advisories and apply official patches or updates as soon as they are released.
- Conduct thorough audits of system logs and user accounts for signs of compromise or unauthorized access.
- Employ network segmentation to limit the impact of a potential breach and contain lateral movement.
- Educate security teams about this vulnerability to ensure rapid detection and response.
Description
An issue in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a remote attacker to obtain sensitive information via a crafted payload to the id parameter in the mliSystemUsers.php component.