FortinacApplication · Fortinet
CVE-2024-31488
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 inputs during web page generation vulnerability [CWE-79] in FortiNAC version 9.4.0 through 9.4.4, 9.2.0 through 9.2.8, 9.1.0 through 9.1.10, 8.8.0 through 8.8.11, 8.7.0 through 8.7.6, 7.2.0 through 7.2.3 may allow a remote authenticated attacker to perform stored and reflected cross site scripting (XSS) attack via 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 · high confidenceA cross-site scripting (XSS) vulnerability in FortiNAC allows remote authenticated attackers to inject malicious scripts via crafted HTTP requests. The flaw affects multiple version ranges (7.2.0-7.2.3, 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.10, 9.2.0-9.2.8, 9.4.0-9.4.4) and enables both stored and reflected XSS attacks due to improper input neutralization during web page generation.
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
>= 7.2.0, < 7.2.4>= 8.7.0, < 9.4.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 FortiNAC version via CLILog into the FortiNAC CLI and run the command 'get system status' or 'version' to retrieve the installed firmware version.Affected if The displayed version falls within 7.2.0-7.2.3, 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.10, 9.2.0-9.2.8, or 9.4.0-9.4.4.
-
Verify web interface accessibilityConfirm that the FortiNAC web UI (HTTPS on port 8443 or 443) is reachable from the network. Attempt to access the login page using a browser or curl command.Affected if The web interface is exposed and reachable from untrusted networks without additional authentication controls.
-
Confirm authentication is required for web accessCheck that the FortiNAC web portal requires valid credentials. Attempt to access protected pages without logging in and verify redirects to the login page occur.Affected if The web interface permits unauthenticated access to endpoints or allows authenticated users to submit requests without session validation.
-
Review HTTP access logs for XSS payloadsInspect FortiNAC web server logs (typically stored in /var/log or accessible via the UI) for suspicious patterns such as <script>, javascript:, onerror=, or other HTML/script injection strings in request parameters.Affected if Log entries contain known XSS attack patterns in URL parameters or form submissions.
A user is affected if their FortiNAC version matches the vulnerable ranges and the web interface accepts authenticated HTTP requests that could contain unsanitized script content.
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.
dbcve · scoped7.2.49.4.5
Apply vendor patches when available; prior to patching, implement WAF rules to filter XSS payloads and ensure output encoding is enforced on affected web endpoints.
Upgrade to the latest patch version in your current branch: FortiNAC 7.2.4, 8.7.7, 8.8.12, 9.1.11, 9.2.9, or 9.4.5 (depending on your current branch)
- 1. Identify current FortiNAC version by navigating to the web UI dashboard or running 'fnsysctl get system status' via CLI
- 2. Confirm the specific version falls within an affected range: 7.2.0-7.2.3, 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.10, 9.2.0-9.2.8, or 9.4.0-9.4.4
- 3. Review the FortiNAC Release Notes for the target fixed version to understand new features and any migration considerations
- 4. Take a complete backup of the FortiNAC configuration via the web UI (System > Maintenance > Backup) or CLI command 'fnsysctl execute backup config','5. If running in a HA cluster, follow Fortinet's documented HA upgrade procedure to upgrade the secondary/standby device first, then promote and upgrade the primary
- 6. Download the firmware image for the appropriate fixed version from Fortinet Customer Support portal: 7.2.4, 8.7.7, 8.8.12, 9.1.11, 9.2.9, or 9.4.5
- 7. Upload the firmware via System > Firmware in the web UI or via CLI 'fnsysctl execute system firmware upload <path>','8. After upgrade completes, verify the new version in the dashboard and confirm XSS vulnerability is resolved by testing previously vulnerable vectors
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortinac
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-2024-31488 — 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-2024-31488 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