dbcve.org
Fortiddos FApplication · Fortinet

CVE-2026-39815

HIGH · 8.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 7.2.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
A improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiDDoS-F 7.2.1 through 7.2.2 may allow attacker to execute unauthorized code or commands via sending 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 FortiDDoS-F versions 7.2.1 through 7.2.2 allows remote attackers to execute unauthorized code or commands via crafted HTTP requests due to improper neutralization of special elements in SQL commands.

MitigationUpgrade FortiDDoS-F to a patched version beyond 7.2.2. If immediate patching is not possible, restrict management interface access to trusted networks and implement web application firewall rules to detect and block malicious SQL payloads in HTTP requests.

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
Fortiddos FApplication
Affected:>= 7.2.1, < 7.2.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. Identify FortiDDoS-F installed version
    Access the FortiDDoS-F management interface or CLI and retrieve the firmware version information. In CLI, this is typically shown on login or via 'get system status' command. Alternatively, check the Dashboard or System > Firmware in the GUI.
    Affected if The installed version is 7.2.1, 7.2.2, or any version within the range >= 7.2.1 and < 7.2.3.
  2. Verify management interface exposure
    Review network configuration to determine if the FortiDDoS-F management interface (HTTP/HTTPS) is accessible from untrusted or external networks. Check firewall policies, interface bindings, and administrative access settings.
    Affected if The management interface is reachable from networks outside your trusted administrative zone, making it vulnerable to remote SQL injection attacks.
  3. Check for WAF protection on management traffic
    Inspect any web application firewall, intrusion prevention system, or reverse proxy positioned in front of the FortiDDoS-F management interface. Determine if rules exist to detect and block SQL injection patterns in HTTP request parameters.
    Affected if No WAF or SQL injection filtering is applied to HTTP traffic destined for the FortiDDoS-F management interface.
  4. Audit existing SQL injection mitigation
    Review FortiDDoS-F configuration for any built-in SQL injection protection features, input validation settings, or authentication requirements for the management web interface.
    Affected if SQL injection input validation is disabled or not configured, and the management interface relies solely on authentication without parameter sanitization.

You are affected if FortiDDoS-F is running version 7.2.1 or 7.2.2 AND the management interface is accessible to potential attackers, as the vulnerability is exploitable through crafted HTTP 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.2.3 or later
Fixed in 7.2.3
Interim mitigation

Upgrade FortiDDoS-F to a patched version beyond 7.2.2. If immediate patching is not possible, restrict management interface access to trusted networks and implement web application firewall rules to detect and block malicious SQL payloads in HTTP requests.

Recommended fix High confidence

FortiDDoS-F 7.2.3

  1. Download the FortiDDoS-F 7.2.3 firmware from the Fortinet Customer Support Portal or FortiGuard
  2. Access the FortiDDoS-F web GUI or CLI management interface
  3. Navigate to System > Firmware or use the 'execute firmware upgrade' command
  4. Upload the version 7.2.3 firmware file
  5. Confirm the upgrade and allow the device to reboot
  6. After reboot, verify the system is running version 7.2.3 using 'get system status' or via the web GUI

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

Fix this in Fortiddos F Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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