dbcve.org
FortisandboxApplication · Fortinet

CVE-2025-52436

CRITICAL · 9.6 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 4.4.8 / 5.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability [CWE-79] vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an unauthenticated attacker to execute 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 confidence

FortiSandbox contains a stored XSS vulnerability (CWE-79) in versions 5.0.0-5.0.1, 4.4.0-4.4.7, 4.2, and 4.0 that allows unauthenticated attackers to inject malicious scripts via crafted requests. The CVSS 9.6 score indicates the vulnerability is easily exploitable and has high impact, likely due to the 'command execution' capability mentioned in the description.

MitigationApply the vendor-supplied patch or upgrade FortiSandbox to a version beyond the affected ranges. If immediate patching is not possible, restrict network access to the FortiSandbox management interface.

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:>= 4.0.0, < 4.4.8>= 5.0.0, < 5.0.2

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 web UI and navigate to System > Dashboard > Status, or run the CLI command: get system status
    Affected if The displayed version falls within 4.0.0 to 4.4.7, or 5.0.0 to 5.0.1 (meaning version is less than 4.4.8 or less than 5.0.2)
  2. Verify the exact version number
    Locate the Firmware Version field in the status page or CLI output
    Affected if Version starts with 4.0.x, 4.2.x, 4.4.x (versions below 4.4.8), or 5.0.0 to 5.0.1 (versions below 5.0.2)
  3. Confirm web management interface is accessible
    Check if FortiSandbox HTTPS admin port (typically 443) is reachable from network segments accessible to untrusted users
    Affected if The management interface is exposed to unauthenticated or untrusted network traffic, as the flaw allows unauthenticated attackers to inject malicious scripts
  4. Review web interface for unexpected scripts
    If accessible, inspect any user-controllable fields in the web UI (such as job comments, report names, or configuration labels) for unexpected script tags
    Affected if Malicious script tags appear in fields that were not intentionally entered by an administrator, indicating potential exploitation

You are affected if your FortiSandbox version is 4.0.0 through 4.4.7 or 5.0.0 through 5.0.1 AND the management interface is network-accessible to untrusted users.

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.8 / 5.0.2 or later
Fixed in 4.4.85.0.2
Interim mitigation

Apply the vendor-supplied patch or upgrade FortiSandbox to a version beyond the affected ranges. If immediate patching is not possible, restrict network access to the FortiSandbox management interface.

Recommended fix High confidence

FortiSandbox 4.4.8 (for 4.x branch) or FortiSandbox 5.0.2 (for 5.x branch)

  1. 1. Identify the current FortiSandbox version by accessing the admin GUI or running 'get system status' in CLI
  2. 2. Determine which branch (4.x or 5.x) is currently deployed to select the appropriate upgrade path
  3. 3. Review FortiSandbox release notes for the target version (4.4.8 or 5.0.2) to understand new features and any migration requirements
  4. 4. Create a complete backup of the FortiSandbox configuration via GUI (System > Maintenance > Backup) or CLI 'execute backup full-config'
  5. 5. If running FortiSandbox 4.0.x-4.4.x, upgrade to version 4.4.8. If running FortiSandbox 5.0.x, upgrade to version 5.0.2
  6. 6. Upload the firmware file via GUI (System > Firmware) or CLI and reboot the system
  7. 7. After upgrade completes, verify the version running is the fixed release (4.4.8 or 5.0.2)
  8. 8. Confirm the vulnerability is remediated by checking the FortiGuard advisory at fortiguard.fortinet.com
Caveat Review release notes for any configuration changes or new dependencies between current version and target fixed version before upgrading

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-2025-52436 — 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-2025-52436 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