# CVE-2020-9287: Path traversal in FortiClientEMS

> An attacker can execute unauthorized code or commands via a network-exploitable untrusted search path vulnerability in FortiClient EMS.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2020
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-jf9v-69vw-p2r3

## What is CVE-2020-9287?

CVE-2020-9287 is a high-severity path traversal vulnerability in Fortinet FortiClientEMS, published on 15 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A untrusted search path vulnerability in Fortinet  may allow attacker to execute unauthorized code or commands via network exploitable

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2020-9287?

It affects 1 product.


Products: Fortinet Forticlient Emergency Management Server.

## How do I fix CVE-2020-9287?

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

## Is CVE-2020-9287 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9287 and fix it if it is affected.

What it is: CVE-2020-9287 is a high-severity path traversal vulnerability in Fortinet FortiClientEMS, published on 15 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9287 in the wild and no public exploit code.

Affected product: Fortinet FortiClientEMS. 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-2020-9287/ (Markdown: https://insights.sbomify.com/CVE-2020-9287/index.md)
```

## Sources

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

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