Fortimanager FirmwareOperating system · Fortinet
CVE-2016-3194
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 · uneditedCross-site scripting (XSS) vulnerability in the address added page in Fortinet FortiManager 5.x before 5.0.12 and 5.2.x before 5.2.6 and FortiAnalyzer 5.x before 5.0.13 and 5.2.x before 5.2.6 allows remote attackers 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 · high confidenceStored XSS vulnerability in the address added page of FortiManager and FortiAnalyzer allows authenticated attackers to inject malicious JavaScript/HTML that executes in browsers of other users viewing the page. The CVSS 6.1 reflects network-exploitability with medium integrity requirements (user interaction needed).
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
= 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
= 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.12CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productRun 'get system status' via FortiManager/FortiAnalyzer CLI or check the System Dashboard in the web UI to confirm whether the device is FortiManager or FortiAnalyzerAffected if The device is FortiManager or FortiAnalyzer
-
Check firmware versionRun 'get system status' via CLI or view the firmware version displayed in the web UI footer or System DashboardAffected if Version is 5.0.0 through 5.0.11 for FortiManager, or 5.0.0, 5.0.2 through 5.0.12 for FortiAnalyzer
-
Verify address management accessNavigate to Policy & Objects > Addresses (or equivalent address configuration page) in the web UI to confirm the feature is accessible to the authenticated user roleAffected if The address configuration page is accessible and the user can add or modify address entries
-
Inspect address entries for injected scriptsReview all address objects in Policy & Objects > Addresses. Check the Address Name, IP/Netmask, and Comment fields for unexpected HTML script tags, javascript: URIs, or on* event handlersAffected if Any address entry contains malicious JavaScript/HTML that was not entered by an authorized administrator
You are affected if the device runs FortiManager 5.0.0-5.0.11 or FortiAnalyzer 5.0.0/5.0.2-5.0.12, and the address management feature is accessible with malicious script injected in any address field.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to FortiManager 5.0.12/5.2.6 or FortiAnalyzer 5.0.13/5.2.6 (or later), or apply available patches. Until patched, sanitize input and limit administrative access.
Fix this in Fortimanager Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-3194 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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