dbcve.org
FortisandboxApplication · Fortinet

CVE-2024-52961

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 4.0.6 / 4.2.8 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 [CWE-78] vulnerability in Fortinet FortiSandbox 5.0.0, FortiSandbox 4.4.0 through 4.4.6, FortiSandbox 4.2.1 through 4.2.7, FortiSandbox 4.0.0 through 4.0.5, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions allows an authenticated attacker with at least read-only permission to execute unauthorized commands via crafted 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

This is an OS command injection vulnerability (CWE-78) in FortiSandbox where improper neutralization of special elements allows an authenticated attacker with at least read-only permission to execute unauthorized operating system commands through crafted HTTP requests.

MitigationUpgrade FortiSandbox to the vendor-provided patched version. As an interim measure, restrict administrative access to trusted IP addresses and disable unnecessary administrative interfaces from untrusted networks.

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.0, < 4.0.6>= 4.2.0, < 4.2.8>= 4.4.0, < 4.4.7= 5.0.0

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. Identify FortiSandbox installed version
    Log into the FortiSandbox CLI or GUI and navigate to the Dashboard or System > Settings to view the firmware version, or run the command: 'get system status' in the CLI
    Affected if The version falls within these ranges: >= 3.0.0 and < 4.0.6, OR >= 4.2.0 and < 4.2.8, OR >= 4.4.0 and < 4.4.7, OR version equals 5.0.0
  2. Verify administrative HTTP access is enabled
    In the FortiSandbox GUI, go to System > Administration > Settings, or in CLI run 'show system interface' to check if the management interface (port1 or others) allows HTTP/HTTPS administrative access from untrusted networks
    Affected if HTTP or HTTPS administrative access is enabled on interfaces reachable from untrusted networks (not limited to trusted IPs)
  3. Confirm presence of user accounts with read-only or higher permission
    In the GUI, navigate to System > Administrators to list admin accounts, or run 'get admin user' in CLI
    Affected if There are one or more administrator or read-only user accounts configured (the vulnerability requires authentication with at least read-only privileges)

Your environment is affected if FortiSandbox version is 3.0.0 through 4.0.5, 4.2.0 through 4.2.7, 4.4.0 through 4.4.6, or exactly 5.0.0 AND the administrative interface is accessible to authenticated users via HTTP.

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.0.6 / 4.2.8 / 4.4.7 or later
Fixed in 4.0.64.2.84.4.7
Interim mitigation

Upgrade FortiSandbox to the vendor-provided patched version. As an interim measure, restrict administrative access to trusted IP addresses and disable unnecessary administrative interfaces from untrusted networks.

Recommended fix High confidence

Upgrade to FortiSandbox 4.0.6, 4.2.8, 4.4.7, or the latest 5.x release (5.0.1 or newer) depending on your current branch

  1. 1. Identify the current FortiSandbox version by logging into the FortiSandbox admin GUI or running 'get system status' in the CLI.
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release.
  3. 3. Back up the FortiSandbox configuration via the admin GUI (System > Maintenance > Backup & Restore) or CLI command 'execute backup full-config' to a secure location.
  4. 4. Review the FortiSandbox release notes for the target version to ensure compatibility with your environment and any special upgrade instructions.
  5. 5. Upgrade the FortiSandbox firmware to one of the fixed versions: 4.0.6, 4.2.8, 4.4.7, or the latest 5.x release (such as 5.0.1 or later).
  6. 6. After the upgrade completes, verify the system is operational by checking the dashboard and running 'get system status' in the CLI.
  7. 7. Confirm the fix by verifying the version matches or exceeds the fixed releases (e.g., show version output should display 4.0.6, 4.2.8, 4.4.7, or 5.0.1+).
  8. 8. Test that the specific functionality used before the upgrade still works correctly.
Caveat Standard upgrade risk applies - test in non-production environment first; review release notes for any configuration or behavior changes between versions

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

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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