HMailServer (6.0.0-B1 Through 6.2.18) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/hmailserver-6.0.0-b1-through-6.2.18/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 11 Nov 2026 14:04:09 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgProgressive Robot hMailServer: SQL injection in database layer (CVE-2026-126617)https://feed.craftedsignal.io/briefs/2026-11-01-cve-2026-126617/Wed, 11 Nov 2026 14:04:09 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-11-01-cve-2026-126617/An SQL injection vulnerability in the database layer of Progressive Robot hMailServer versions 6.0.0-B1 through 6.2.18 allows remote attackers to alter SQL statements when using MySQL, MariaDB, or PostgreSQL.Progressive Robot hMailServer 6.0.0-B1 through 6.2.18 contains a SQL injection vulnerability in the SQLStatement::GenerateFromCommand function. The application performs improper parameter binding by performing string replacements on SQL statements rather than using bound parameters. When configured to use MySQL, MariaDB, or PostgreSQL, an attacker can provide input containing parameter names that, when processed, escape the intended SQL literal and inject arbitrary SQL commands. The injected code executes with the privileges of the database service account. SQL Server and SQL Server Compact are not affected as they correctly utilize bound parameters.

Impact

Successful exploitation allows for unauthorized execution of SQL commands with the privileges of the mail server database account. On PostgreSQL, the vulnerability supports command stacking, enabling subsequent arbitrary SQL statements. On MySQL and MariaDB, exploitation is limited to the scope of the original statement.

Recommendation

  • Upgrade hMailServer to a version beyond 6.2.18 immediately once a security update is released by Progressive Robot.
  • Audit database user privileges to follow the principle of least privilege, ensuring the database account used by hMailServer has the minimum necessary access to perform its functions.
  • If the environment permits, transition to SQL Server or SQL Server Compact to utilize bound parameters, as these configurations are not susceptible to this specific flaw.
  • Review mail server logs for anomalous recipient addresses or metadata patterns that indicate injection attempts.
]]>highadvisory