dbcve.org
FortindrApplication · Fortinet

CVE-2026-25088

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 7.4.10 / 7.6.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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 FortiNDR 7.6.0 through 7.6.2, FortiNDR 7.4.0 through 7.4.9, FortiNDR 7.2 all versions, FortiNDR 7.1 all versions, FortiNDR 7.0 all versions may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP 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 · moderate confidence

SQL injection vulnerability in Fortinet FortiNDR allows authenticated attackers to execute unauthorized code or commands via specifically crafted HTTP requests. The vulnerability affects multiple version ranges (7.0 through 7.6.2) and stems from improper neutralization of special elements in SQL commands.

MitigationApply vendor-supplied patches/updates to upgrade FortiNDR to the latest fixed version. Until patched, restrict administrative interface access to trusted networks and implement additional input validation as a compensating control.

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
FortindrApplication
Affected:>= 7.0.0, < 7.4.10>= 7.6.0, < 7.6.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm FortiNDR is installed
    Identify if Fortinet FortiNDR is present in your environment by reviewing installed software or consulting your asset inventory
    Affected if FortiNDR software is found in your environment
  2. Check installed FortiNDR version
    Locate the installed version of FortiNDR (typically viewable in the web UI under System > Settings or via CLI command 'get system status') and compare it to the affected ranges: 7.0.0 - 7.4.10 or 7.6.0 - 7.6.2
    Affected if Installed version falls within >= 7.0.0 and < 7.4.10, or >= 7.6.0 and < 7.6.3
  3. Verify web interface accessibility
    Determine if the FortiNDR web administrative interface is exposed to network access (check firewall rules, ACLs, or interface bindings)
    Affected if The administrative interface is accessible from untrusted networks (the vulnerability requires authenticated access)
  4. Review access logs for suspicious SQL patterns
    Examine FortiNDR logs (typically found in Log & Report or via CLI) for unusual SQL syntax, error messages containing SQL keywords, or unexpected database errors that may indicate exploitation attempts
    Affected if Log entries show SQL injection patterns or unexplained SQL errors from authenticated sessions

You are affected if FortiNDR is running a version within 7.0.0-7.4.10 or 7.6.0-7.6.2 and the administrative interface is accessible to attackers who can obtain valid credentials.

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.10 / 7.6.3 or later
Fixed in 7.4.107.6.3
Interim mitigation

Apply vendor-supplied patches/updates to upgrade FortiNDR to the latest fixed version. Until patched, restrict administrative interface access to trusted networks and implement additional input validation as a compensating control.

Recommended fix High confidence

FortiNDR 7.4.10 or later, or FortiNDR 7.6.3 or later

  1. 1. Backup current FortiNDR configuration and ensure you have a recovery plan.
  2. 2. For FortiNDR 7.4.x deployments: upgrade to version 7.4.10 or later.
  3. 3. For FortiNDR 7.6.x deployments: upgrade to version 7.6.3 or later.
  4. 4. For FortiNDR 7.0.x, 7.1.x, and 7.2.x deployments: these versions have reached end-of-life; upgrade to a supported branch (7.4.10+ or 7.6.3+).
  5. 5. After upgrade, verify the system is operational and confirm the SQL injection vulnerability is remediated.
  6. 6. Test that normal FortiNDR functionality (detection, reporting, API access) continues to work as expected.
Caveat Older branches (7.0.x, 7.1.x, 7.2.x) are end-of-life and require migration to 7.4.x or 7.6.x

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

Fix this in Fortindr Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25088 — 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-2026-25088 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