FortisandboxApplication · Fortinet
CVE-2024-52960
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 · uneditedA client-side enforcement of server-side security vulnerability [CWE-602] in Fortinet FortiSandbox version 5.0.0, 4.4.0 through 4.4.6 and before 4.2.7 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 · moderate confidenceThis is a CWE-602 (Client-Side Enforcement of Server-Side Security) vulnerability in Fortinet FortiSandbox where an authenticated attacker with read-only permissions can execute unauthorized commands via crafted HTTP requests. The vulnerability stems from the server trusting client-side security controls that can be bypassed.
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.0.0, < 4.2.8>= 4.4.0, < 4.4.7= 5.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiSandbox installationLocate the FortiSandbox instance by checking for the web service on its management interface port (default 443 or 8080), or check system services for 'fortisandbox' processes using commands like 'ps aux | grep -i sandbox' or 'systemctl list-units | grep -i sandbox'Affected if FortiSandbox is not present in the environment
-
Determine FortiSandbox versionAccess the FortiSandbox web UI and navigate to System > Settings > About, or use the CLI command 'get system status' to retrieve the firmware versionAffected if The installed version cannot be determined or is not listed
-
Compare version against affected rangesCheck if the identified version falls within: 3.0.0 <= version < 4.2.8, OR 4.4.0 <= version < 4.4.7, OR version equals 5.0.0 exactlyAffected if The version matches any of these three ranges: 3.0.0 through 4.2.7, 4.4.0 through 4.4.6, or 5.0.0
The environment is affected if FortiSandbox is running and its version falls within 3.0.0 to <4.2.8, 4.4.0 to <4.4.7, or equals exactly 5.0.0, allowing an authenticated read-only user to potentially bypass client-side security controls via crafted HTTP requests.
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 data4.2.84.4.7
Upgrade FortiSandbox to version 4.2.7 or later, or to the latest patched releases for 4.4.x and 5.0.x branches as specified in Fortinet's security advisory.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52960 — 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-52960 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