FortinacApplication · Fortinet
CVE-2022-40676
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 improper neutralization of input during web page generation ('cross-site scripting') in Fortinet FortiNAC versions 9.4.0, 9.2.0 through 9.2.5, 9.1.0 through 9.1.8, 8.8.0 through 8.8.11, 8.7.0 through 8.7.6, 8.6.0 through 8.6.5, 8.5.0 through 8.5.4, 8.3.7 allows attacker to execute unauthorized code or commands via specially crafted http requests.
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 · moderate confidenceA cross-site scripting (XSS) vulnerability in FortiNAC allows attackers to inject malicious scripts via specially crafted HTTP requests. The improper neutralization of input during web page generation enables execution of unauthorized code or commands through the injected payload.
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.5.0, <= 8.5.4>= 8.6.0, <= 8.6.5>= 8.7.0, <= 8.7.6>= 8.8.0, <= 8.8.11>= 9.1.0, <= 9.1.8>= 9.2.0, <= 9.2.5= 8.3.7= 9.4.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.1/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.
-
Identify the installed FortiNAC versionLog into the FortiNAC admin web UI and navigate to System > Settings > General, or use the CLI command to display system version information (typically via fnsysctl or show system status commands)Affected if The displayed version falls within any of these ranges: 8.5.0-8.5.4, 8.6.0-8.6.5, 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.8, 9.2.0-9.2.5, or equals exactly 8.3.7 or 9.4.0
-
Confirm the FortiNAC web interface is accessibleVerify that the FortiNAC web administration portal (HTTPS on port 443 or configured admin port) is reachable and responsiveAffected if The web interface is exposed and accessible to network users or attackers, as this XSS vulnerability is exploited via specially crafted HTTP requests to the web application
-
Check if remote administrative access is enabledReview FortiNAC network settings to determine if HTTP/HTTPS administrative access is permitted from non-localhost sourcesAffected if Remote web management is enabled, allowing external attackers to send malicious HTTP requests containing XSS payloads to the application
You are affected if your FortiNAC version matches any of the listed vulnerable versions AND the web interface is accessible, since exploitation requires sending crafted HTTP requests to the web application.
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 dataApply the vendor patch/upgrade to a fixed version of FortiNAC (9.4.1 or later for the 9.x branch, or the latest available fixed version for other affected branches).
Fix this in Fortinac
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40676 — 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-2022-40676 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