FortiwebApplication · Fortinet
CVE-2017-7736
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 · uneditedA stored Cross-site Scripting (XSS) vulnerability in Fortinet FortiWeb webUI Certificate View page in 5.8.0, 5.7.1 and earlier, allows attackers to inject arbitrary web script or HTML via special crafted malicious certificate import.
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 Cross-site Scripting (XSS) vulnerability exists in Fortinet FortiWeb's web UI Certificate View page. Attackers can inject arbitrary web script or HTML by importing a specially crafted malicious certificate, which gets stored and executes when other users view the certificate in the web 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
FortiwebApplication
<= 5.7.1= 5.8.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check FortiWeb versionLog into the FortiWeb CLI or web UI and navigate to System > Status to view the firmware version. Alternatively, run 'get system status' in the CLI.Affected if The installed version is 5.7.1 or earlier, or exactly 5.8.0
-
Verify web UI is enabledIn FortiWeb web UI, go to System > Network > Interface and confirm the administrative web interface (HTTPS) is enabled on an accessible port.Affected if The web UI is accessible and certificate viewing is possible by users
-
Review imported certificatesIn the web UI, navigate to Server Objects > Certificates > Local and inspect all certificates listed. Look for any certificates with unexpected or anomalous names, or certificates that were imported around the time of potential attack.Affected if There are certificates present in the store that were imported via untrusted sources or contain XSS payloads in certificate fields (subject, issuer, SAN fields)
-
Check certificate import logsIn the web UI, go to Log & Report > Event Log and filter for certificate-related events (certificate import, upload, or modify actions). Review the timing and source of certificate imports.Affected if Certificate import events exist from untrusted sources or during periods of suspicious activity
You are affected if your FortiWeb version is 5.7.1 or earlier, or exactly 5.8.0, AND the web UI is accessible allowing users to view imported certificates.
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 FortiWeb version 5.7.2, 5.8.1, or later which contain the patch. Alternatively, implement input validation and output encoding on certificate import and display functions.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7736 — 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-2017-7736 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