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

Stored XSS in Fortinet FortiSandbox LDAP server option

IdentifiersCVE-2025-53608CWE-79· Improper Neutralization of Input…

CVE-2025-53608 is a stored cross-site scripting vulnerability in Fortinet FortiSandbox, caused by improper neutralization of input during web page generation. According to the provided content, the issue affects FortiSandbox 5.0.0 through 5.0.2, 4.4.0 through 4.4.7, and all versions in the 4.2 and 4.0 branches. The vulnerability is specifically associated with the LDAP server option and allows an authenticated privileged attacker to inject malicious script content via crafted requests. When the stored payload is later rendered in the FortiSandbox web interface, attacker-controlled code can execute in the victim’s browser session.

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 enables execution of attacker-supplied script in the context of the FortiSandbox web application for users who view the maliciously stored content. This can lead to session hijacking, theft of administrative tokens or credentials, unauthorized actions performed through the victim’s browser, interface manipulation, and potential follow-on compromise of the management plane depending on the privileges of the user who loads the payload. Because the issue is stored XSS and requires privileged authenticated access to plant the payload, the practical impact is highest in multi-admin environments.

Mitigation

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

Until patches are applied, restrict access to the FortiSandbox administrative interface to trusted administrators only, minimize the number of privileged accounts, and monitor for suspicious or unexpected changes involving the LDAP server option. Review audit and administrative logs for crafted configuration changes, and consider isolating the management interface from untrusted networks. Because exploitation requires authenticated privileged access, enforcing strong access controls and reducing exposure of the web management interface lowers risk.

Remediation

Patch, then assume compromise.

Upgrade FortiSandbox to a fixed release provided by Fortinet and verify installed versions against the vendor advisory for CVE-2025-53608 / FG-IR-26-091. Affected versions listed in the provided content are 5.0.0 through 5.0.2, 4.4.0 through 4.4.7, and all versions of 4.2 and 4.0. Administrators should apply the vendor patch or move to a non-affected supported version as identified in the FortiGuard PSIRT advisory.
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

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 activity1

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