# CVE-2017-3131: Cross-site scripting in Fortinet FortiOS

> Attackers can execute unauthorized code via XSS in FortiView filter input, requiring FortiOS upgrades.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 12 Sep 2017
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-vpwv-v7qq-9vj6

## What is CVE-2017-3131?

CVE-2017-3131 is a medium-severity cross-site scripting vulnerability in Fortinet Fortios, published on 12 Sep 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Scripting vulnerability in Fortinet FortiOS versions 5.4.0 through 5.4.4 and 5.6.0 allows attackers to execute unauthorized code or commands via the filter input in "Applications" under FortiView.

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

## Which versions are affected by CVE-2017-3131?

It affects 1 product.


Products: Fortinet Fortios.

## How do I fix CVE-2017-3131?

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

## Is CVE-2017-3131 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3131 exists.

Public exploit code:

- Fortinet FortiOS < 5.6.0 - Cross-Site Scripting (exploitdb)
- FortiOS 5.4.0 to 5.6.0 - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-3131.yaml

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3131 and fix it if it is affected.

What it is: CVE-2017-3131 is a medium-severity cross-site scripting vulnerability in Fortinet Fortios, published on 12 Sep 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3131 exists.

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

## Sources

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

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