dbcve.org
FortisandboxApplication · Fortinet

CVE-2025-53679

HIGH · 7.2 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 4.4.8 / 5.0.3 or later.
See remediation →
78/100
Remediation priority · High
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 ('OS Command Injection') vulnerability [CWE-78] vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.2, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions, FortiSandbox Cloud 24.1, FortiSandbox Cloud 23 all versions allows a remote privileged attacker to execute unauthorized code or commands via crafted HTTP or HTTPS 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 Fortinet FortiSandbox allows remote privileged attackers to execute unauthorized commands via crafted HTTP/HTTPS requests. The flaw exists in the web management interface and affects multiple version branches including 5.0.x, 4.4.x, 4.2.x, and 4.0.x, as well as FortiSandbox Cloud versions.

MitigationApply vendor-supplied patches/updates to reach a supported, non-vulnerable version. Restrict administrative access to trusted networks and disable unnecessary management interfaces until patching is complete.

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:>= 4.0.0, < 4.4.8>= 5.0.0, < 5.0.3
Fortisandbox CloudApplication
Affected:>= 23.1.4245, < 23.4.4374= 24.1.4436

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify FortiSandbox product and version
    Access the web management interface and check System > FortiSandbox > System Information or run 'get system status' via CLI to retrieve the exact version number and product type (FortiSandbox vs FortiSandbox Cloud)
    Affected if The version falls within 4.0.0 to 4.4.7, 5.0.0 to 5.0.2, 23.1.4245 to 23.4.4373, or equals 24.1.4436
  2. Verify web management interface is accessible
    Attempt to reach the HTTPS management portal (default ports 443 or 8443) or check in System > Administration > Administrators to confirm web UI access is enabled
    Affected if The web management interface is exposed and reachable (even from internal networks, the vulnerability still applies to remote privileged attackers)
  3. Confirm administrative accounts exist
    Check System > Administrators in the web UI or run 'get admin user' via CLI to enumerate accounts with administrative privileges
    Affected if Any privileged administrative accounts exist on the system, as the vulnerability allows remote privileged attackers to execute commands

You are affected if your FortiSandbox or FortiSandbox Cloud version matches the affected ranges AND the web management interface is accessible with any administrative account present.

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 4.4.8 / 5.0.3 / 23.4.4374 or later
Fixed in 4.4.85.0.323.4.4374
Interim mitigation

Apply vendor-supplied patches/updates to reach a supported, non-vulnerable version. Restrict administrative access to trusted networks and disable unnecessary management interfaces until patching is complete.

Recommended fix Moderate confidence

FortiSandbox 4.4.8, 5.0.3 or later; FortiSandbox Cloud 23.4.4374 or later, 24.2 or later

  1. 1. Identify the current FortiSandbox version by navigating to System > Firmware or using the CLI command 'get system status'
  2. 2. For FortiSandbox 4.x (versions 4.0.0-4.4.7): Download and install firmware version 4.4.8 or later from Fortinet Customer Support portal
  3. 3. For FortiSandbox 5.x (versions 5.0.0-5.0.2): Download and install firmware version 5.0.3 or later from Fortinet Customer Support portal
  4. 4. For FortiSandbox Cloud 23.x (versions 23.1.4245-23.4.4373): Upgrade to version 23.4.4374 or later through FortiCloud management console
  5. 5. For FortiSandbox Cloud 24.1.x (specifically 24.1.4436): Upgrade to a version beyond 24.1.4436 (such as 24.2.x or later) through FortiCloud management console
  6. 6. After upgrade, verify the fix by confirming the new version is installed and running 'get system status' in CLI
  7. 7. Review system logs to ensure no unauthorized command execution occurred during the vulnerable period
Caveat Standard firmware upgrade - review Fortinet release notes for any configuration or compatibility notes before applying

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

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53679 — 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-2025-53679 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