Skip to main content
VulnerabilityPublished Updated

CVE-2024-24133: atmail · SQL Injection

Affects atmailSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Feb 2024

  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

Affected software

ProductAffectedFixed in
GitHubhebing123/atmailpkg:github/hebing123/atmailOther threatsAffected
  • =6.6.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-24133, organizations should immediately implement the following measures: 1) Apply strict input validation and sanitization on the username parameter at the application level, employing parameterized queries or prepared statements to prevent SQL injection. 2) Deploy or update Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the login page. 3) Monitor logs and network traffic for anomalous patterns indicative of SQL injection attempts, such as unusual query strings or error messages. 4) Restrict database user permissions to the minimum necessary, limiting the potential damage from successful injection. 5) If possible, isolate the Atmail server behind additional security layers and restrict access to trusted IP ranges. 6) Engage with Atmail support or vendor channels to obtain patches or official guidance as soon as they become available. 7) Consider temporary alternative authentication mechanisms or multi-factor authentication to reduce risk exposure. 8) Conduct penetration testing and code reviews focused on input handling to identify and remediate similar vulnerabilities.

Description

Atmail v6.6.0 was discovered to contain a SQL injection vulnerability via the username parameter on the login page.

References

Community reviews

Loading reviews…