dbcve.org
FortisandboxApplication · Fortinet

CVE-2021-26097

HIGH · 8.8 CVSS v3.1 Published 2021-08-04
Fix available
A fix is available. Upgrade to 3.0.7 / 3.1.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An improper neutralization of special elements used in an OS Command vulnerability in FortiSandbox 3.2.0 through 3.2.2, 3.1.0 through 3.1.4, and 3.0.0 through 3.0.6 may allow an authenticated attacker with access to the web GUI to execute unauthorized code or commands via specifically 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 confidence

OS command injection vulnerability in FortiSandbox web GUI allows authenticated attackers to execute arbitrary OS commands via specially crafted HTTP requests. The flaw affects versions 3.0.0-3.0.6, 3.1.0-3.1.4, and 3.2.0-3.2.2, enabling complete system compromise post-authentication.

MitigationUpgrade FortiSandbox to a patched version beyond 3.2.2, 3.1.4, or 3.0.6 as provided by Fortinet's security advisory.

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
Affected:< 3.0.7>= 3.1.0, < 3.1.5>= 3.2.0, < 3.2.3

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine FortiSandbox installed version
    Run 'fortisandbox -v' or access the web GUI and check System > Firmware or the login page footer for the version number
    Affected if The version falls within 3.0.0-3.0.6, 3.1.0-3.1.4, or 3.2.0-3.2.2
  2. Confirm web GUI is enabled
    Check FortiSandbox system settings via CLI: 'get system interface' or inspect the web GUI login page is reachable on port 443
    Affected if The web GUI interface is active and accessible on the network
  3. Verify authentication is configured
    Check user accounts exist: 'get system admin' via CLI or verify local user authentication is enabled in System > Administration > Administrators
    Affected if Administrative or user accounts are configured, allowing authenticated access to the web GUI
  4. Identify exposed management interfaces
    Review network configuration: 'get system interface' and check for management-facing IPs or port exposure via 'diagnose system netstat'
    Affected if The web GUI port (default 443) is exposed to untrusted networks or directly accessible from external IPs

You are affected if FortiSandbox version is 3.0.0-3.0.6, 3.1.0-3.1.4, or 3.2.0-3.2.2 AND the web GUI with authentication is accessible, enabling a remote authenticated attacker to inject commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.0.7 / 3.1.5 / 3.2.3 or later
Fixed in 3.0.73.1.53.2.3
Interim mitigation

Upgrade FortiSandbox to a patched version beyond 3.2.2, 3.1.4, or 3.0.6 as provided by Fortinet's security advisory.

Recommended fix High confidence

FortiSandbox 3.2.3 or later (recommended: latest stable 3.2.x release)

  1. Identify the current FortiSandbox version using the web GUI or CLI command 'get system status'
  2. Determine which version branch your current installation falls into (3.0.x, 3.1.x, or 3.2.x)
  3. Download the appropriate fixed version from Fortinet support portal: upgrade to 3.0.7 or later for 3.0.x branch, 3.1.5 or later for 3.1.x branch, or 3.2.3 or later for 3.2.x branch
  4. Back up the FortiSandbox configuration before upgrading
  5. Upload and install the firmware upgrade via the web GUI (System > Firmware) or CLI (execute upgrade)
  6. After upgrade, verify the version using 'get system status' and confirm the vulnerability is resolved
  7. Review user access controls and consider limiting web GUI access to trusted users only, as this vulnerability requires authenticated access
Caveat Review Fortinet release notes for the target version for any configuration or feature changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26097 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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