FortiClient Hit by Severe SQL Injection Vulnerability Enabling Database Intrusion
## Fortinet FortiClient EMS Security Flaw
Fortinet FortiClient EMS Security Flaw
Cybersecurity researchers have identified a critical security vulnerability in Fortinet’s FortiClient Enterprise Management Server (EMS), tracked as CVE-2026-21643. This pre-authentication SQL injection vulnerability has a CVSS severity score of 9.1, allowing unauthenticated attackers to execute arbitrary SQL commands and gain control over the underlying database.
The flaw is specific to multi-tenant deployments of FortiClient EMS version 7.4.4, posing a significant risk to corporate network data. It originates from a code update during the release of version 7.4.4, where Fortinet developers refactored the software’s middleware that connects web requests to the database. An error in handling the HTTP "Site" header, which identifies different tenant environments, was introduced.
The vulnerability allows attackers to exploit the system by sending a single web request to the /api/v1/init_consts endpoint, which lacks rate-limiting protections and returns database error messages directly. This enables attackers to extract sensitive data rapidly using error-based extraction techniques.
The flaw is specific to multi-tenant deployments of FortiClient EMS version 7.4.4, posing a significant risk to corporate network data.
Successful exploitation allows attackers to gain database administrator-level access, enabling them to steal administrative passwords, harvest security certificates, and map out managed endpoints. Additionally, with superuser privileges, attackers can execute commands on the server’s operating system, potentially leading to a complete network takeover.
The vulnerability is limited to FortiClient EMS version 7.4.4 with the multi-tenant "Sites" feature enabled. Versions prior to 7.4.4 and the newer 8.0 release are unaffected. Fortinet resolved the issue in version 7.4.5 by implementing proper sanitization of HTTP header inputs.
Organizations using the affected version are strongly advised to upgrade immediately. Security teams should monitor Apache access logs for unusual response times or unexpected HTTP 500 errors on the /api/v1/init_consts endpoint to detect potential intrusions. Disabling the multi-tenant feature or restricting web access to the EMS interface can temporarily mitigate the risk.
Based on reporting by GBHackers.
