FortinacApplication · Fortinet
CVE-2019-5594
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 During Web Page Generation ("Cross-site Scripting") in Fortinet FortiNAC 8.3.0 to 8.3.6 and 8.5.0 admin webUI may allow an unauthenticated attacker to perform a reflected XSS attack via the search field in the webUI.
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 reflected cross-site scripting (XSS) vulnerability in FortiNAC's admin web interface. The search field in the webUI fails to properly sanitize user-supplied input, allowing an unauthenticated attacker to inject malicious JavaScript code via a crafted URL. When a victim clicks the malicious link and interacts with the search field, the injected script executes in the user'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
FortinacApplication
>= 8.3.0, <= 8.3.6= 8.5.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.
-
Confirm FortiNAC installationVerify that Fortinet FortiNAC is deployed in your environment. Check your asset inventory or run system commands to identify the product (for example, review running services or installed packages that indicate FortiNAC).Affected if FortiNAC is not present in your environment - you are not affected.
-
Determine installed FortiNAC versionAccess the FortiNAC CLI or admin web interface and retrieve the current software version. Typically available in the system dashboard or via 'get system status' command in CLI.Affected if The installed version falls within 8.3.0 through 8.3.6 inclusive, or is exactly 8.5.0 - continue to next check.
-
Verify admin webUI is network-accessibleDetermine if the FortiNAC admin web interface (typically ports 443 or 8080) is accessible from networks outside your trusted internal segments. Review firewall rules, ACLs, or VPN policies governing access to the webUI.Affected if The admin webUI is exposed to untrusted or external networks - the reflected XSS can be triggered via crafted links sent to authenticated users.
-
Confirm search field is reachableLog into the FortiNAC admin web interface and navigate to any page containing the search functionality (such as the global search bar). Verify that user-supplied input in the search field is reflected in the response without proper encoding.Affected if The search field reflects unsanitized input in the page output - the vulnerability is present and exploitable.
You are affected if FortiNAC version is 8.3.0-8.3.6 or 8.5.0 AND the admin webUI is accessible to untrusted users who could send malicious links to authenticated administrators.
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 dataUpdate FortiNAC to a version beyond 8.3.6 or 8.5.0 (or apply vendor-supplied patches). As a compensating control, restrict access to the admin webUI to trusted networks only until the patch can be applied.
Fix this in Fortinac
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5594 — 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-2019-5594 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