dbcve.org
Fortimanager FirmwareOperating system · Fortinet

CVE-2016-3193

MEDIUM · 5.4 CVSS v3.0 Published 2016-08-19
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 the appliance web-application in Fortinet FortiManager 5.x before 5.0.12, 5.2.x before 5.2.6, and 5.4.x before 5.4.1 and FortiAnalyzer 5.x before 5.0.13, 5.2.x before 5.2.6, and 5.4.x before 5.4.1 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.

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

Stored XSS vulnerability in FortiManager and FortiAnalyzer appliance web interfaces. Authenticated users can inject malicious JavaScript/HTML into unspecified input fields, which executes when other users view the injected content.

MitigationApply vendor patches: upgrade to FortiManager/FortiAnalyzer 5.0.12+, 5.2.6+, or 5.4.1+. Until patched, implement input validation on user-supplied fields and consider 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.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.0.11
Fortianalyzer FirmwareOperating system
Affected:= 5.0.0= 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.0.11= 5.0.12

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 the installed product
    Log into the FortiManager/FortiAnalyzer CLI and run 'get system status' or access the web UI and check the dashboard for the product name
    Affected if The product is FortiManager or FortiAnalyzer
  2. Check firmware version
    Run 'get system status' in CLI or view the version in the web UI dashboard. Compare the version number to the affected ranges: FortiManager 5.0.0-5.0.11, FortiAnalyzer 5.0.0-5.0.12
    Affected if The installed firmware version matches any of the listed affected versions
  3. Verify web interface is accessible
    Confirm the web-based management interface (HTTPS on port 443 or configured port) is enabled and reachable. Check with 'get system interface' in CLI to see HTTP/HTTPS status
    Affected if The web interface is enabled and accessible to users
  4. Determine if multiple users exist
    Check for multiple administrative accounts using 'get admin user' in CLI or review user list in web UI under User & Device > User Definition
    Affected if Multiple authenticated users or administrators exist in the system
  5. Audit stored content for injected scripts
    Review database entries in the system where user-supplied data is stored (such as device names, policy descriptions, or custom fields). Use CLI queries like 'get device' or inspect log entries for unexpected HTML/JavaScript patterns
    Affected if Unexpected script tags or HTML attributes are found in stored user-defined fields

A system is affected if it runs FortiManager firmware 5.0.0-5.0.11 or FortiAnalyzer firmware 5.0.0-5.0.12, has the web interface enabled, and contains malicious script content injected by an authenticated user in any input field.

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

Apply vendor patches: upgrade to FortiManager/FortiAnalyzer 5.0.12+, 5.2.6+, or 5.4.1+. Until patched, implement input validation on user-supplied fields and consider Content Security Policy headers.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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