Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

SQL Injection in Fortinet FortiAnalyzer JSON-RPC API

IdentifiersCVE-2025-49784CWE-89· Improper Neutralization of Special…

CVE-2025-49784 is an SQL injection vulnerability in Fortinet FortiAnalyzer and FortiAnalyzer-BigData, tracked by Fortinet as FG-IR-26-095. The issue is caused by improper neutralization of special elements used in SQL commands. According to the provided content, the flaw is exposed through the FortiAnalyzer JSON-RPC API and affects FortiAnalyzer 7.6.0 through 7.6.4, 7.4.0 through 7.4.7, all versions in the 7.2, 7.0, and 6.4 branches, as well as FortiAnalyzer-BigData 7.6.0, 7.4.0 through 7.4.4, and all versions in the 7.2, 7.0, 6.4, and 6.2 branches. A remote authenticated attacker can send specifically crafted requests to the vulnerable interface to trigger the SQL injection condition, which may result in execution of unauthorized code or commands.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an authenticated attacker to execute unauthorized code or commands on the affected FortiAnalyzer or FortiAnalyzer-BigData system. Given the product role, compromise could also enable unauthorized interaction with backend data and administrative functions exposed through the vulnerable API. The provided content specifically states code or command execution as the primary impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the FortiAnalyzer JSON-RPC API to trusted administrative networks only, minimize the number of accounts permitted to authenticate to the interface, and monitor API and administrative logs for anomalous crafted requests or unexpected command execution behavior. Where feasible, disable or isolate external exposure of the management/API interface until updates are applied. These are risk-reduction measures only; the primary mitigation is vendor patching.

Remediation

Patch, then assume compromise.

Upgrade affected FortiAnalyzer and FortiAnalyzer-BigData deployments to a vendor-fixed release as identified by Fortinet in its PSIRT advisory for FG-IR-26-095 / CVE-2025-49784. Administrators should verify installed versions against the affected version list and apply the appropriate patched version from Fortinet. Because broad version ranges are affected, organizations should consult the FortiGuard PSIRT advisory to determine the exact fixed build for each supported branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortianalyzeroperating_system
FortinetFortianalyzer Big Dataapplication
FortinetFortianalyzer-Bigdataapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.