# CVE-2024-31487: Path traversal in FortiSandbox

> Attackers can disclose sensitive information via crafted HTTP requests exploiting a path traversal flaw in FortiSandbox.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N/E:F/RL:X/RC:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-39m6-4cjh-f5fx

## What is CVE-2024-31487?

CVE-2024-31487 is a medium-severity path traversal vulnerability in Fortinet Fortisandbox, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.4, FortiSandbox 4.2.1 through 4.2.6, FortiSandbox 4.0 all versions, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions, FortiSandbox 2.5 all versions, FortiSandbox 2.4 all versions allows attacker to information disclosure via crafted http requests.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-31487?

It affects 1 product.


Products: Fortinet Fortisandbox.

## How do I fix CVE-2024-31487?

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

## Is CVE-2024-31487 being exploited?

There is no known exploitation of CVE-2024-31487 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-2024-31487 and fix it if it is affected.

What it is: CVE-2024-31487 is a medium-severity path traversal vulnerability in Fortinet Fortisandbox, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31487 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-2024-31487/ (Markdown: https://insights.sbomify.com/CVE-2024-31487/index.md)
```

## Sources

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

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