dbcve.org
FortianalyzerApplication · Fortinet

CVE-2025-49784

HIGH · 7.2 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.4.5 / 7.4.8 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer 6.4 all versions, FortiAnalyzer-BigData 7.6.0, FortiAnalyzer-BigData 7.4.0 through 7.4.4, FortiAnalyzer-BigData 7.2 all versions, FortiAnalyzer-BigData 7.0 all versions, FortiAnalyzer-BigData 6.4 all versions, FortiAnalyzer-BigData 6.2 all versions may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in FortiAnalyzer allows authenticated attackers to execute unauthorized code or commands via specifically crafted SQL requests. The vulnerability affects multiple version ranges across FortiAnalyzer and FortiAnalyzer-BigData platforms.

MitigationApply Fortinet security patches to upgrade affected FortiAnalyzer installations to vendor-supported versions. Since authentication is required, ensure compromised credentials are rotated and monitor for unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortianalyzerApplication
Affected:>= 6.4.0, < 7.4.8>= 7.6.0, < 7.6.5
Fortianalyzer Big DataApplication
Affected:>= 6.2.1, < 7.4.5= 7.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FortiAnalyzer version
    Run 'get system status' via CLI or check the System > Settings page in the web UI to identify the exact firmware version installed
    Affected if The installed version falls within 7.4.0 through 7.4.7, 7.6.0 through 7.6.4, or is 6.4.0 through 7.4.7 (for versions below 7.0)
  2. Identify product type
    Check if the installed system is FortiAnalyzer or FortiAnalyzer Big Data by reviewing the system status output or web UI product name
    Affected if The product is FortiAnalyzer Big Data and the version is 6.2.1 through 7.4.4 or exactly 7.6.0
  3. Verify SQL database feature is in use
    Check if the SQL logging or reporting feature is enabled in the system configuration (Log Settings or SQL Settings in the web UI)
    Affected if SQL database features are enabled and the version is vulnerable
  4. Check for exposed admin interfaces
    Review network configuration to determine if the admin GUI or CLI is accessible from untrusted networks
    Affected if The admin interface is exposed to the internet or untrusted networks, increasing the likelihood of credential compromise

The environment is affected if FortiAnalyzer or FortiAnalyzer Big Data is running a version within the affected ranges and the SQL database feature is enabled, making it vulnerable to SQL injection via authenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.5 / 7.4.8 / 7.6.5 or later
Fixed in 7.4.57.4.87.6.5
Interim mitigation

Apply Fortinet security patches to upgrade affected FortiAnalyzer installations to vendor-supported versions. Since authentication is required, ensure compromised credentials are rotated and monitor for unauthorized access.

Recommended fix High confidence

FortiAnalyzer: upgrade to 7.4.8 or 7.6.5 (or later); FortiAnalyzer-Big Data: upgrade to 7.4.5 or 7.6.1 (or later)

  1. 1. Identify the exact FortiAnalyzer version currently installed using: 'get system status' in the CLI or via the web UI under System Settings > Dashboard > System Information.
  2. 2. For FortiAnalyzer (standard): If running version 7.4.x (7.4.0 through 7.4.7), upgrade to version 7.4.8 or later. If running version 7.6.x (7.6.0 through 7.6.4), upgrade to version 7.6.5 or later.
  3. 3. For FortiAnalyzer-Big Data: If running version 7.4.x (7.4.0 through 7.4.4), upgrade to version 7.4.5 or later. If running version 7.6.0, upgrade to version 7.6.1 or later.
  4. 4. For versions 7.2.x, 7.0.x, 6.4.x, and 6.2.x, contact Fortinet support for specific patch availability or migration path to a supported version.
  5. 5. Download the firmware from the Fortinet Customer Support Portal: https://customer.fortinet.com/ and review the release notes for upgrade instructions.
  6. 6. Back up the FortiAnalyzer configuration before performing the upgrade.
  7. 7. Upload and install the new firmware via the web UI (System Settings > Firmware) or CLI using 'execute restore' commands, following Fortinet's upgrade procedure.
  8. 8. After upgrade, verify the version and ensure the vulnerability is resolved by confirming the fix is applied.
Caveat Review Fortinet release notes for any configuration changes or migration steps between major versions; some legacy features may require reconfiguration after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49784 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data