Skip to main content
VulnerabilityPublished Updated

CVE-2024-45438: TitanHQ SpamTitan Email Security Gateway · Missing Authentication

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in 8.01.14 : patch affected systems as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.01.14, 8.00.101
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

  1. Immediate application of vendor patches: Organizations should upgrade SpamTitan Email Security Gateway to versions 8.00.101, 8.01.14, or later where this vulnerability is fixed.
  2. If patching is not immediately possible, restrict access to the SpamTitan management interface, especially quarantine.php, by implementing network-level controls such as IP whitelisting, VPN access, or firewall rules limiting access to trusted administrators only.
  3. Monitor web server logs for suspicious GET requests to quarantine.php, particularly those containing unusual or non-existent email addresses, to detect potential exploitation attempts.
  4. Implement multi-factor authentication (MFA) and strong access controls for administrative interfaces to reduce the risk of unauthorized access.
  5. Conduct regular audits of user accounts and quarantine settings to identify unauthorized changes or newly created user records.
  6. Employ intrusion detection/prevention systems (IDS/IPS) to detect anomalous traffic patterns targeting the SpamTitan interface.
  7. Educate IT and security teams about this vulnerability and ensure incident response plans include steps to handle potential exploitation scenarios. These targeted mitigations go beyond generic advice by focusing on access restriction, monitoring, and administrative controls specific to the vulnerable component.

Description

An issue was discovered in TitanHQ SpamTitan Email Security Gateway 8.00.x before 8.00.101 and 8.01.x before 8.01.14. The file quarantine.php within the SpamTitan interface allows unauthenticated users to trigger account-level actions using a crafted GET request. Notably, when a non-existent email address is provided as part of the email parameter, SpamTitan will automatically create a user record and associate quarantine settings with it - all without requiring authentication.

References

Community reviews

Loading reviews…