dbcve.org
FortisandboxApplication · Fortinet

CVE-2025-61886

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 5.0.5 or later.
See remediation →
61/100
Remediation priority · Elevated
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.4, FortiSandbox PaaS 5.0.0 through 5.0.4 may allow an attacker to perform an XSS attack 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 · high confidence

FortiSandbox versions 5.0.0 through 5.0.4 contain a stored or reflected XSS vulnerability (CWE-79) where crafted HTTP requests are not properly sanitized before being rendered in web pages. An attacker can inject malicious JavaScript that executes in the context of other users' sessions when they view the affected content.

MitigationUpgrade FortiSandbox to version 5.0.5 or later. If immediate upgrade is not possible, implement WAF rules to filter malicious HTTP request patterns and restrict administrative access to trusted IP addresses.

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:>= 5.0.0, < 5.0.5
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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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. Check FortiSandbox version
    Log into the FortiSandbox CLI and run: get system status OR access the web UI and navigate to Dashboard > System Information to view the firmware version
    Affected if The displayed version is 5.0.0, 5.0.1, 5.0.2, 5.0.3, or 5.0.4 (FortiSandbox Cloud version 5.0.4 also affected)
  2. Confirm web interface is enabled
    In the CLI, run: get system interface OR check via web UI under Network > Interfaces to verify the mgmt or http/https interface is enabled
    Affected if The web administrative interface (HTTP or HTTPS) is accessible on any interface
  3. Review HTTP access logs for suspicious patterns
    In the web UI, go to Log & Report > Event Logs > System Events and search for unusual HTTP parameters or requests containing script tags, javascript:, or similar XSS patterns
    Affected if Any log entries show injected script content in HTTP request parameters
  4. Check user session logs for anomalous script execution
    Review Log & Report > Event Logs > Admin Events for any unexpected JavaScript-related errors or alerts, or check the SQL database directly if accessible
    Affected if Any admin event logs indicate XSS payload execution or anomalous JavaScript behavior

Your environment is affected if FortiSandbox version is 5.0.0 through 5.0.4 and the web administrative interface is 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 5.0.5 or later
Fixed in 5.0.5
Interim mitigation

Upgrade FortiSandbox to version 5.0.5 or later. If immediate upgrade is not possible, implement WAF rules to filter malicious HTTP request patterns and restrict administrative access to trusted IP addresses.

Recommended fix High confidence

FortiSandbox >= 5.0.5

  1. Upgrade FortiSandbox to version 5.0.5 or later
  2. For FortiSandbox Cloud customers, ensure your cloud instance is updated to version 5.0.5 or later
  3. After upgrade, verify the XSS vulnerability is remediated by reviewing release notes or consulting Fortinet support
Caveat Review Fortinet release notes for any configuration or behavioral changes between 5.0.x and 5.0.5

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

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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