FortiosOperating system · Fortinet
CVE-2020-15937
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 · uneditedAn improper neutralization of input vulnerability in FortiGate version 6.2.x below 6.2.5 and 6.4.x below 6.4.1 may allow a remote attacker to perform a stored cross site scripting attack (XSS) via the IPS and WAF logs dashboard.
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 confidenceA stored XSS vulnerability in FortiGate IPS and WAF logs dashboard allows attackers to inject malicious JavaScript that executes when users view the affected logs. The vulnerability stems from improper neutralization of user-supplied input in the logging interface.
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
FortiosOperating system
>= 6.2.0, < 6.2.5>= 6.4.0, < 6.4.1CVSS 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.1/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.
-
Check the FortiOS versionRun the command `get system status` or `fortios -v` on the FortiGate CLI to retrieve the installed FortiOS version numberAffected if The displayed version falls within >= 6.2.0 and < 6.2.5, or >= 6.4.0 and < 6.4.1
-
Determine if IPS logging is enabledIn the FortiGate web UI or CLI, navigate to the IPS configuration and check whether IPS logging to the local logs dashboard is turned onAffected if IPS logging is enabled and users have access to view IPS logs through the dashboard
-
Determine if WAF logging is enabledIn the FortiGate web UI or CLI, navigate to the WAF configuration and check whether WAF logging to the local logs dashboard is turned onAffected if WAF logging is enabled and users have access to view WAF logs through the dashboard
-
Inspect IPS and WAF logs for injected script contentReview recent entries in the IPS and WAF log dashboards using the web UI or by exporting logs via `execute log filter` commands, looking for log entries that contain unexpected HTML tags, script elements, or JavaScript function callsAffected if Any log entries display unescaped HTML or script content when viewed in the dashboard
You are affected if your FortiOS version is within the vulnerable ranges AND the IPS or WAF logging feature is enabled with dashboard access for users.
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 data6.2.56.4.1
Upgrade FortiGate to version 6.2.5 or 6.4.1 or later to remediate. Until patched, limit access to the IPS and WAF logs dashboard to trusted administrators only.
Fix this in Fortios
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15937 — 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-2020-15937 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