FortisandboxApplication · Fortinet
CVE-2026-39813
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 path traversal: '../filedir' vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8 may allow attacker to escalation of privilege via specially 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 confidenceA path traversal vulnerability exists in FortiSandbox versions 4.4.0-4.4.8 and 5.0.0-5.0.5 where specially crafted HTTP requests containing '../filedir' sequences allow attackers to traverse directories and escalate privileges. The vulnerability stems from insufficient input validation on HTTP request parameters.
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
>= 4.4.0, < 4.4.9>= 5.0.0, < 5.0.6CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed versionAccess the FortiSandbox CLI and run: 'get system status' or check the GUI dashboard to view the firmware version. Alternatively, use SNMP or the API endpoint to retrieve the system version.Affected if The displayed version falls within 4.4.0 through 4.4.8, or 5.0.0 through 5.0.5 (or is earlier than 4.4.0). Versions 4.4.9 and above, or 5.0.6 and above, are not affected.
-
Verify HTTP management interface exposureCheck network configuration via 'config system interface' in CLI to identify which interfaces have 'set ip <address> <netmask>' and confirm management access methods. Look for interfaces with 'set allowaccess https http' that are reachable from untrusted networks.Affected if HTTP or HTTPS management interfaces are exposed to untrusted networks or the internet without restrictive ACLs.
-
Inspect logs for path traversal patternsReview FortiSandbox logs using 'execute log filter' and 'execute log display' or access the log viewer in the GUI. Search for entries containing '../' or '..\' patterns in request paths, especially those containing 'filedir' or similar directory traversal sequences.Affected if Logs show HTTP requests containing '../filedir' or similar path traversal sequences, indicating potential exploitation attempts.
-
Check for unauthorized privilege escalationReview system logs and user account audit logs via the GUI or CLI 'execute log filter category event' for new administrative accounts, changed user permissions, or unusual administrative actions that coincide with the timeframe of potential path traversal requests.Affected if New administrative accounts exist or privilege changes occurred that were not initiated by legitimate administrators.
You are affected if FortiSandbox is running version 4.4.0-4.4.8 or 5.0.0-5.0.5 AND the HTTP management interface is externally accessible AND suspicious path traversal requests appear in logs or unexpected privilege changes occurred.
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.
dbcve · scoped4.4.95.0.6
Apply Fortinet's latest patch for FortiSandbox to remediate the path traversal vulnerability. Alternatively, restrict HTTP access to FortiSandbox management interfaces to trusted networks only as a compensating control until patching is feasible.
FortiSandbox 4.4.9 or FortiSandbox 5.0.6 (depending on your current major version branch)
- 1. Identify the currently installed FortiSandbox version via the web UI (System > Dashboard > Status) or CLI: 'get system status'
- 2. For FortiSandbox 4.4.x installations: Upgrade to version 4.4.9 or later
- 3. For FortiSandbox 5.0.x installations: Upgrade to version 5.0.6 or later
- 4. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com)
- 5. In the FortiSandbox web UI, go to System > Firmware and upload the new firmware file
- 6. Wait for the upgrade to complete and verify the new version is installed
- 7. Confirm the vulnerability is remediated by reviewing the system after upgrade
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
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 locallyCheck whether your project pulls in CVE-2026-39813 — 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-2026-39813 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