Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Stored XSS in FortiSandbox and FortiSandbox PaaS

IdentifiersCVE-2026-39812CWE-79· Improper Neutralization of Input…

CVE-2026-39812 is a stored cross-site scripting vulnerability in Fortinet FortiSandbox and FortiSandbox PaaS. The provided content identifies it as an improper neutralization of input during web page generation issue affecting FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8, FortiSandbox 4.2 all versions, FortiSandbox PaaS 5.0.0 through 5.0.5, FortiSandbox PaaS 4.4.0 through 4.4.8, and FortiSandbox PaaS 4.2 all versions; another supporting mention narrows affected versions to FortiSandbox and FortiSandbox PaaS 5.0.1 through 5.0.5. The issue is described as stored XSS, meaning attacker-controlled input can be persisted by the application and later rendered in a victim’s browser without proper output encoding or sanitization. The exact vulnerable parameter, page, or function is not provided in the available content.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could allow execution of attacker-supplied script in the browser context of a user viewing the affected FortiSandbox or FortiSandbox PaaS interface. Depending on the victim’s privileges and session state, this could enable session hijacking, theft of sensitive interface data, unauthorized actions performed as the victim, interface defacement, or use of the administrative web UI as a pivot for further compromise. The supplied content also generically states the flaw may allow an attacker to execute unauthorized code or commands, but based on the available details this is best understood as client-side script execution via stored XSS rather than confirmed server-side command execution.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure to the FortiSandbox web interface by restricting access to trusted administrative networks and users only, minimizing the number of accounts with GUI access, and monitoring for suspicious or unexpected content rendered in the interface. Because this is stored XSS, review user-supplied or persisted fields in the application for malicious payloads and clear any identified injected content where feasible. These are compensating measures only; vendor patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade FortiSandbox and FortiSandbox PaaS to a fixed release identified by Fortinet. The provided content confirms that Fortinet issued fixes for CVE-2026-39812, but does not include the exact remediated version beyond indicating affected ranges. Organizations should follow the corresponding Fortinet PSIRT advisory for FG-IR-26-110 and move to the vendor-recommended patched version on each affected branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortisandboxapplication
FortinetFortisandbox Cloudapplication
FortinetFortisandboxpaasapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.