dbcve.org
Fortimanager FirmwareOperating system · Fortinet

CVE-2016-3196

MEDIUM · 5.4 CVSS v3.0 Published 2016-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Cross-site scripting (XSS) vulnerability in Fortinet FortiAnalyzer 5.x before 5.0.12 and 5.2.x before 5.2.6 and FortiManager 5.x before 5.0.12 and 5.2.x before 5.2.6 allows remote authenticated users to inject arbitrary web script or HTML via the filename of an image uploaded in the report section.

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

This is a stored cross-site scripting (XSS) vulnerability in FortiAnalyzer and FortiManager where authenticated users can inject arbitrary HTML or JavaScript through the filename parameter when uploading an image in the report section. The malicious payload is stored and executed when other users view the affected report.

MitigationUpgrade to FortiAnalyzer/FortiManager version 5.0.12 or 5.2.6 or later. As a compensating control, restrict report upload permissions to trusted users only and implement Content Security Policy headers.

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.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= 5.2.1= 5.2.2= 5.2.3
Fortianalyzer FirmwareOperating system
Affected:= 5.0.0= 5.0.1= 5.0.4= 5.0.5= 5.0.10= 5.2.0= 5.2.1= 5.2.2= 5.2.3= 5.2.4= 5.2.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 product and firmware version
    Run 'get system status' or 'fnsysctl get system status' via CLI to display the running firmware version and product name (FortiManager or FortiAnalyzer).
    Affected if The firmware version matches any of: FortiManager 5.0.3 through 5.2.3 (specific builds 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, 5.2.1, 5.2.2, 5.2.3) or FortiAnalyzer 5.0.0 through 5.2.5 (specific builds 5.0.0, 5.0.1, 5.0.4, 5.0.5, 5.0.10, 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2
  2. Verify report upload functionality is accessible
    Check if users have access to the report section where image uploads are permitted. This is typically under Reports > Report Definitions or similar in the web UI, or check user role permissions via 'get system admin user' CLI command.
    Affected if Authenticated users have permissions to create or upload reports containing images.
  3. Audit existing reports for suspicious filenames
    Review stored reports in the report database. In the CLI, use 'execute sql-local list report' or access the reports section in the web UI and inspect any uploaded image filenames for unusual characters or script tags.
    Affected if Any stored reports contain image filenames with HTML script tags, JavaScript event handlers, or other XSS payloads in the filename field.

You are affected if your FortiAnalyzer or FortiManager firmware version is one of the listed affected builds AND users with report upload permissions exist in your environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FortiAnalyzer/FortiManager version 5.0.12 or 5.2.6 or later. As a compensating control, restrict report upload permissions to trusted users only and implement Content Security Policy headers.

Fix this in Fortimanager Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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