# CVE-2020-6647: Cross-site scripting in Fortinet FortiADC

> An authenticated attacker can execute cross-site scripting attacks via the name parameter in the FortiADC dashboard.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Apr 2020
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-g9g7-5v3p-474j

## What is CVE-2020-6647?

CVE-2020-6647 is a medium-severity cross-site scripting vulnerability in Fortinet FortiADC, published on 7 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An improper neutralization of input vulnerability in the dashboard of FortiADC may allow an authenticated attacker to perform a cross site scripting attack (XSS) via the name parameter.

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

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

It affects 1 product.


Products: Fortinet Fortiadc Firmware.

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

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

## Is CVE-2020-6647 being exploited?

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

## Other vulnerabilities in Fortinet FortiADC

- [CVE-2020-9286](https://insights.sbomify.com/CVE-2020-9286/): Missing authorization in FortiADC (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6647 is a medium-severity cross-site scripting vulnerability in Fortinet FortiADC, published on 7 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-6647 in the wild and no public exploit code.

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

## Sources

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

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