dbcve.org
FortisandboxApplication · Fortinet

CVE-2024-54026

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 4.4.7 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 sql command ('sql injection') in Fortinet FortiSandbox 4.4.0 through 4.4.6, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions, FortiSandbox Cloud 24.1 allows attacker 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

SQL injection vulnerability in FortiSandbox allows remote attackers to execute unauthorized code or commands via crafted HTTP requests due to improper neutralization of special elements in SQL commands.

MitigationApply vendor-provided patches/updates for affected FortiSandbox versions; implement input validation and least-privilege database accounts as compensating controls until full patch deployment.

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.4.7
Fortisandbox CloudApplication
Affected:= 24.1

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 version via CLI
    Log into the FortiSandbox CLI and run the command: 'get system status' or 'fortisandbox -v' to retrieve the firmware version.
    Affected if The displayed version falls within 3.0.0 to 4.4.6, or is exactly 24.1 for FortiSandbox Cloud.
  2. Verify web interface is enabled
    In the FortiSandbox CLI, run 'get system interface' or check the web UI access settings to confirm the management web interface (HTTP/HTTPS) is enabled and accessible.
    Affected if The web interface is enabled and exposed, making it reachable over the network.
  3. Check network exposure of management interface
    Review firewall or network ACL rules to determine if the FortiSandbox management port (typically 443 or 80) is exposed to untrusted networks or the internet.
    Affected if The management interface is accessible from untrusted networks or the internet.
  4. Confirm FortiSandbox Cloud version
    If using FortiSandbox Cloud service, check the service version or subscription details to confirm it is version 24.1.
    Affected if The FortiSandbox Cloud version is exactly 24.1.

A system is affected if it runs FortiSandbox firmware between 3.0.0 and 4.4.6 inclusive, FortiSandbox Cloud version 24.1, and has the web management interface enabled and accessible.

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

Apply vendor-provided patches/updates for affected FortiSandbox versions; implement input validation and least-privilege database accounts as compensating controls until full patch deployment.

Recommended fix High confidence

FortiSandbox >= 4.4.7; FortiSandbox Cloud > 24.1

  1. 1. Back up the FortiSandbox configuration and all critical data before proceeding with the upgrade
  2. 2. Download the FortiSandbox firmware version 4.4.7 or later from the Fortinet Customer Support portal
  3. 3. Access the FortiSandbox web interface or CLI
  4. 4. Navigate to System > Firmware or use the 'execute firmware' CLI command
  5. 5. Upload and install the firmware version 4.4.7
  6. 6. After installation, verify the system boots successfully and all services are running
  7. 7. Confirm the version upgrade was successful by checking System > Dashboard > Status
  8. 8. For FortiSandbox Cloud customers, ensure your deployment is updated to the latest available version beyond 24.1
Caveat Review Fortinet release notes for 4.4.7 for any configuration or behavioral changes before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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