dbcve.org
Fortimanager FirmwareOperating system · Fortinet

CVE-2015-3616

CRITICAL · 9.8 CVSS v3.0 Published 2017-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SQL injection vulnerability in Fortinet FortiManager 5.0.x before 5.0.11, 5.2.x before 5.2.2 allows remote attackers to execute arbitrary commands via unspecified parameters.

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 Fortinet FortiManager 5.0.x before 5.0.11 and 5.2.x before 5.2.2 allows remote attackers to execute arbitrary commands via unspecified parameters. The CVSS 9.8 score indicates this is remotely exploitable without authentication and leads to complete compromise of the system.

MitigationUpgrade FortiManager to version 5.0.11 or later, or 5.2.2 or later, to remediate this vulnerability. If immediate patching is not possible, restrict network access to the FortiManager management interfaces to trusted networks only.

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
Fortimanager FirmwareOperating system
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 target is FortiManager
    Access the web login page or use CLI command 'get system status' and look for 'FortiManager' in the product name or hostname
    Affected if The device is FortiManager
  2. Check firmware version
    In CLI run 'get system status' or via web GUI go to System > FortiGuard > Firmware to view the current firmware version
    Affected if Version shows 5.0.x where x is 0-10, or version 5.2.0
  3. Verify management interface is exposed
    Check if HTTP (port 80) or HTTPS (port 443) management ports are listening on the FortiManager IP address using 'netstat -an' or a port scanner
    Affected if The web interface ports 80/443 are open and accessible from the network where the check is performed

If the device is FortiManager running firmware 5.0.0 through 5.0.10 or firmware 5.2.0, and the management web interface is network-accessible, then the environment is affected by CVE-2015-3616.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FortiManager to version 5.0.11 or later, or 5.2.2 or later, to remediate this vulnerability. If immediate patching is not possible, restrict network access to the FortiManager management interfaces to trusted networks only.

Recommended fix High confidence

FortiManager 5.0.11 or later (or migrate to a newer major version such as 5.2.x or 6.x with equivalent or later security patches)

  1. 1. Back up current FortiManager configuration and data.
  2. 2. Download FortiManager firmware version 5.0.11 or later from Fortinet's support portal (https://support.fortinet.com/).
  3. 3. Access FortiManager web UI or CLI.
  4. 4. Navigate to System > Firmware or use CLI command 'execute restore image' to upload the firmware.
  5. 5. Boot the new firmware image.
  6. 6. Verify the upgrade was successful by checking the firmware version in System > Dashboard > System Information.
  7. 7. Confirm normal operation of managed devices and configurations.
Caveat Review FortiManager release notes for 5.0.11 for any configuration changes or deprecated features; major version jumps (e.g., 5.0 to 5.2 or 6.x) may require additional migration steps.

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

Fix this in Fortimanager Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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