# CVE-2025-53608: Cross-site scripting in FortiSandbox

> An authenticated privileged attacker can execute code via crafted requests due to a cross-site scripting vulnerability in FortiSandbox.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:P/RL:X/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-q2rj-vh69-cw5h

## What is CVE-2025-53608?

CVE-2025-53608 is a medium-severity cross-site scripting vulnerability in Fortinet Fortisandbox, published on 10 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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.2, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an authenticated privileged attacker to execute code via crafted requests.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-53608?

It affects 1 product.


Products: Fortinet Fortisandbox.

## How do I fix CVE-2025-53608?

No fix has been published for CVE-2025-53608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53608 being exploited?

There is no known exploitation of CVE-2025-53608 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet Fortisandbox

- [CVE-2026-25089](https://insights.sbomify.com/CVE-2026-25089/): Fortinet FortiSandbox OS Command Injection (critical 9.1, exploited in the wild)
- [CVE-2026-39808](https://insights.sbomify.com/CVE-2026-39808/): Fortinet FortiSandbox OS Command Injection (critical 9.1, exploited in the wild)
- [CVE-2026-26083](https://insights.sbomify.com/CVE-2026-26083/): Missing authorization in FortiSandbox (critical 9.1)
- [CVE-2026-39813](https://insights.sbomify.com/CVE-2026-39813/): Path traversal in FortiSandbox (critical 9.1)
- [CVE-2020-29011](https://insights.sbomify.com/CVE-2020-29011/): SQL injection in Fortinet FortiSandbox (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53608 and fix it if it is affected.

What it is: CVE-2025-53608 is a medium-severity cross-site scripting vulnerability in Fortinet Fortisandbox, published on 10 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-53608 in the wild and no public exploit code.

Affected product: Fortinet Fortisandbox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53608/ (Markdown: https://insights.sbomify.com/CVE-2025-53608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53608
- OSV: https://osv.dev/vulnerability/CVE-2025-53608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53608/
Summaries are generated and may contain mistakes; the official description above is the record.