Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2017-3132: XSS in Fortinet FortiOS FortiToken Activation

Published Sep 12, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.1Medium · v3
EPSS8.1%95th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Fortinet
IdentifiersCVE-2017-3132CWE-79 · Improper Neutralization of Input…

CVE-2017-3132 is a Cross-Site Scripting (XSS) vulnerability in Fortinet FortiOS versions 5.6.0 and earlier. The vulnerability exists in the handling of the 'action' input parameter during the activation process of a FortiToken. Improper sanitization of this input allows attackers to inject and execute arbitrary scripts in the context of the user's browser session.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to execute unauthorized code or commands in the context of the affected user's session. This can lead to session hijacking, credential theft, or further compromise of the management interface.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the FortiOS management interface to trusted networks and users. Employ web application firewalls or input validation proxies to filter malicious input. Educate users to avoid clicking on suspicious links or interacting with untrusted sources while authenticated to the management interface.

Remediation

Patch, then assume compromise.

Upgrade FortiOS to a version later than 5.6.0 where this vulnerability has been addressed. Fortinet has released patches to properly sanitize user input during FortiToken activation.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortiosoperating_system
FAQ

Frequently asked questions

Is CVE-2017-3132 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-3132 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-3132?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2017-3132.
Is there a patch for CVE-2017-3132?
Upgrade FortiOS to a version later than 5.6.0 where this vulnerability has been addressed. Fortinet has released patches to properly sanitize user input during FortiToken activation.
What products are affected by CVE-2017-3132?
Fortinet Fortios.
How severe is CVE-2017-3132?
CVE-2017-3132 has a CVSS v3 score of 6.1 (Medium) and an EPSS score of 8.1% (95th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.