dbcve.org
Fortisandbox CloudApplication · Fortinet

CVE-2026-25836

HIGH · 7.2 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 in Fortinet FortiSandbox Cloud 5.0.4, FortiSandbox PaaS 5.0.4 may allow a privileged attacker with super-admin profile and CLI access to execute unauthorized code or commands via 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 · moderate confidence

OS command injection vulnerability in FortiSandbox Cloud/PaaS 5.0.4 allows a privileged attacker with super-admin profile and CLI access to execute unauthorized commands via crafted HTTP requests due to improper neutralization of special elements in OS command contexts.

MitigationApply Fortinet vendor patch when available; restrict super-admin access and CLI permissions to only necessary personnel; monitor for anomalous HTTP requests and command execution.

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
Fortisandbox CloudApplication
Affected:= 5.0.4

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 type
    Log into the FortiSandbox web UI or CLI and run the command: get system status. Verify the product type shows as 'FortiSandbox Cloud' or 'FortiSandbox PaaS'.
    Affected if The product is FortiSandbox Cloud or FortiSandbox PaaS
  2. Check installed firmware version
    In the web UI, go to Dashboard > Status or run: get system status in CLI. Look for the Firmware/Version field.
    Affected if Version displayed is exactly 5.0.4
  3. Verify super-admin profile configuration
    In the web UI, go to System > Administrators > Administrators. Review the list of admin accounts and check if any have the 'super_admin' profile or super-admin privileges assigned.
    Affected if At least one account has super-admin or super_admin profile enabled
  4. Confirm CLI access is available
    In the web UI, go to System > Administrators > Administrators. For each admin account, check if CLI access is permitted (the 'CLI' checkbox or permission is enabled for any admin profile).
    Affected if CLI access is enabled for any administrator account

You are affected if you are running FortiSandbox Cloud/PaaS version 5.0.4 and have any super-admin profile with CLI access enabled in your environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Fortinet vendor patch when available; restrict super-admin access and CLI permissions to only necessary personnel; monitor for anomalous HTTP requests and command execution.

Recommended fix Moderate confidence

Contact Fortinet for the specific fixed version (check FortiGuard for FortiSandbox Cloud 5.0.4 patched release)

  1. 1. Contact Fortinet Technical Support or check FortiGuard (fortiguard.fortinet.com) for the latest available fixed version of FortiSandbox
  2. 2. Request and apply the specific patch or upgrade to the fixed release as indicated by Fortinet for version 5.0.4
  3. 3. After upgrading, verify the fix by confirming the OS command injection vulnerability is no longer present
  4. 4. Review admin profiles and CLI access permissions to ensure adherence to least-privilege principles
Caveat Review Fortinet release notes for any configuration or behavioral changes between 5.0.4 and the fixed version before upgrading

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

Fix this in Fortisandbox Cloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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