FortianalyzerApplication · Fortinet
CVE-2018-13375
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 Script-Related HTML Tags in Fortinet FortiAnalyzer 5.6.0 and below and FortiManager 5.6.0 and below allows an attacker to send DHCP request containing malicious scripts in the HOSTNAME parameter. The malicious script code is executed while viewing the logs in FortiAnalyzer and FortiManager (with FortiAnalyzer feature enabled).
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 confidenceThis is a stored/stored Cross-Site Scripting (XSS) vulnerability in FortiAnalyzer and FortiManager. Attackers inject malicious JavaScript code through the DHCP HOSTNAME parameter, which gets stored in logs. When administrators view these logs in the web interface, the unsanitized hostname is rendered and the script executes in the administrator's browser context.
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
FortianalyzerApplication
<= 5.6.0
FortimanagerApplication
<= 5.6.0CVSS 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 FortiAnalyzer or FortiManager installation and versionRun CLI command 'get system status' or check the web UI at System Settings > System > About to retrieve the firmware versionAffected if The version is 5.6.0 or lower, indicating the product is within the affected range
-
Confirm web interface is enabledCheck via CLI: 'get system interface' or 'show system interface' to verify the management interface has HTTP/HTTPS access enabledAffected if The web interface (HTTPS/HTTP) is accessible, which is required for the XSS to trigger when logs are viewed
-
Verify DHCP logging is activeCheck log settings via CLI: 'get log syslogd setting' or navigate to Log & Report > Log Settings in the web UI to confirm DHCP events are being loggedAffected if DHCP logging is enabled and storing hostname information in system logs
-
Inspect stored DHCP log entries for unsanitized contentNavigate to Log & Report > System Events > DHCP in the web UI, or run 'execute log filter category 24' and review entries for the 'hostname' fieldAffected if DHCP log entries exist and contain raw, unescaped hostname data that could include script tags
You are affected if FortiAnalyzer or FortiManager version 5.6.0 or lower is running, the web interface is enabled, DHCP logging stores hostname data, and those logs can be viewed by administrators in the web UI.
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 FortiAnalyzer/FortiManager version 6.0.0 or later to receive the vendor patch. Alternatively, restrict access to log viewing functions to highly trusted administrators and implement network segmentation to limit exposure to malicious DHCP requests.
Fix this in Fortianalyzer
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13375 — 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-2018-13375 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