SQL Injection in Fortinet FortiAnalyzer and FortiManager Enables Code or Command Execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-126262?

CVE-2026-126262 is a vulnerability classified as Improper Neutralization of Special Elements used in an SQL Command, affecting FortiAnalyzer (affected versions: 8.0.0 – ≤ 8.0.1, 7.6.0 – ≤ 7.6.7, and other affected versions) and FortiManager (affected versions: 8.0.0, 7.6.0 – ≤ 7.6.7, and other affected versions). This vulnerability is rated Critical, with a CVSS score of 9.8. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

A improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12 may allow an unauthenticated attacker who has access to the oftp port to execute code or command on the system via crafted OFTP packets.

Affected products and scope

Fortinet marks the default status as unaffected outside the explicitly listed ranges below. The status of branches not present in the record is not independently established.

  • FortiAnalyzer: 8.0.0 through 8.0.1; 7.6.0 through 7.6.7; 7.4.0 through 7.4.11; 7.2.0 through 7.2.12.
  • FortiManager: 8.0.0; 7.6.0 through 7.6.7; 7.4.0 through 7.4.11; 7.2.0 through 7.2.12.

Technical details

The flaw is classified as CWE-89 and arises when special elements in attacker-controlled input are not properly neutralized before being used in an SQL command. The input arrives in crafted OFTP packets, and the attacker must be able to reach the OFTP port; authentication is not required. If processing reaches the vulnerable path, the record states that the attacker may execute code or commands on the system. The OFTP handler, SQL statement, database, execution context, and required packet structure are not disclosed. The affected scope in the record is limited to the listed FortiAnalyzer and FortiManager releases.

Exploitability

Reachability is network-based and depends on access to the OFTP port. No authentication or user interaction is required, and the supplied attack characteristics describe low attack complexity. The normalized record does not state whether exploitation has been observed, whether a public exploit exists, or whether the issue is included in an active exploitation catalog. It also does not provide exploit code or packet details.

Technical impact

Successful exploitation may permit code or command execution within the affected system. This could potentially lead to data disclosure, configuration or data modification, and service disruption on the appliance. The record does not identify the privilege context in which the code or command runs, so the highest administrative privilege should not be assumed. Access to the OFTP port remains an important reachability limitation, but authentication is not required before sending the crafted input.

Business impact

  • System compromise: Successful exploitation may allow code or command execution on a FortiAnalyzer or FortiManager appliance.
  • Data and configuration risk: Possible consequences include unauthorized access to, or modification of, data and configuration handled or stored by the appliance.
  • Service risk: An attacker may be able to disrupt the appliance or functions that depend on it.
  • The actual consequence depends on OFTP reachability, the system's role in the environment, and the permissions available to the vulnerable process. The record does not confirm a breach, data loss, or specific exploitation campaign.

Remediation

  1. Upgrade FortiManager to the fixed release corresponding to the deployed branch: 8.0.1, 7.6.8, 7.4.12, or 7.2.13.
  2. Upgrade FortiAnalyzer to the fixed release corresponding to the deployed branch: 8.0.2, 7.6.8, 7.4.12, or 7.2.13.
  3. Until upgrades are complete, restrict access to the OFTP port to trusted systems or peers. This is a risk-reduction measure inferred from the stated access precondition, not a vendor-confirmed workaround.
  4. Validate every appliance after upgrading and compare its release with the applicable product branch. The record provides only the upgrade targets above and does not confirm an additional workaround.

Detection

  1. Inventory all deployed FortiAnalyzer and FortiManager instances, then compare each release with the affected branches and fixed targets listed in this entry.
  2. Verify whether the OFTP port is reachable from untrusted or broader-than-necessary networks; review related firewall, ACL, NAT, and load-balancer rules.
  3. Review network telemetry for unexpected connections or malformed OFTP packets and correlate them with unexpected process execution, command activity, or configuration changes on the appliances. Treat this as precautionary monitoring because the record provides no confirmed indicator or log signature.
  4. If OFTP exposure is found, prioritize remediation and preserve relevant network and system logs for investigation. The absence of suspicious events does not prove that a system is safe.
Sources (19)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.