CVE-2024-32371: HSC Cybersecurity HC Mailinspector · Improper Input Validation
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 52% 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:N/A:NExploitation 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
Organizations should immediately assess their deployment of HC Mailinspector versions 5.2.17-3 through 5.2.18 and prioritize upgrading to a patched version once available. In the absence of an official patch, implement strict network segmentation to limit access to the Mailinspector management interfaces only to trusted administrators. Employ application-layer firewalls or Web Application Firewalls (WAFs) to monitor and block suspicious parameter manipulations, specifically targeting changes to the 'type' parameter. Conduct thorough access reviews to ensure that regular user accounts have minimal privileges and monitor logs for unusual privilege escalation attempts. Additionally, implement multi-factor authentication (MFA) for administrative access to reduce the risk of compromised credentials being exploited. Regularly audit and update security policies related to email security infrastructure to detect and respond to potential exploitation attempts promptly.
Description
An issue in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a regular user account to escalate their privileges and gain administrative access by changing the type parameter from 1 to 0.