FortisandboxApplication · Fortinet
CVE-2021-24014
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 · uneditedMultiple instances of improper neutralization of input during web page generation vulnerabilities in FortiSandbox before 4.0.0 may allow an unauthenticated attacker to perform an XSS attack via specifically crafted request parameters.
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 confidenceMultiple stored XSS vulnerabilities in FortiSandbox web interface allow unauthenticated attackers to inject malicious scripts through specially crafted HTTP request parameters. The input is not properly sanitized before being rendered in web pages, enabling script execution in victim browsers.
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
FortisandboxApplication
<= 3.1.4>= 3.2.0, < 3.2.3CVSS 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.1/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 FortiSandbox versionAccess the FortiSandbox CLI or admin web interface and retrieve the firmware version. In the CLI, run: get system status. On the web UI, the version is typically displayed on the login page or in System > Firmware. Compare this version number against the affected ranges: <= 3.1.4 or >= 3.2.0 and < 3.2.3.Affected if The installed version falls within <= 3.1.4 or >= 3.2.0 to < 3.2.3.
-
Verify web interface is enabledIn FortiSandbox, check if the web UI service is active. From CLI, run: get system interface. Look for the management interface configuration. Alternatively, check HTTP/HTTPS service status: diagnose system webui get.Affected if The web interface (HTTP/HTTPS on ports 80 or 443 or custom ports) is enabled and accessible.
-
Check web interface network exposureReview the network interface binding for the web service. From CLI, run: show system interface and examine which interface(s) the web UI is bound to. Determine if it listens on external-facing interfaces or is restricted to internal networks.Affected if The web interface is bound to or accessible from untrusted/external networks rather than being limited to trusted management networks.
Your environment is affected if FortiSandbox version is 3.1.4 or earlier, or between 3.2.0 and 3.2.2, and the web interface is enabled and accessible from your network.
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 data3.2.3
Upgrade FortiSandbox to version 4.0.0 or later to patch the XSS vulnerabilities. If immediate upgrade is not possible, consider restricting access to the web interface to trusted networks only.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24014 — 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-2021-24014 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