# CVE-2017-6803: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to change admin passwords, stop the scheduler, or execute arbitrary commands in SolarWinds FTP Voyager.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hxr9-qvr4-wf99

## What is CVE-2017-6803?

CVE-2017-6803 is a high-severity vulnerability in n/a, published on 20 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in the web interface in the Scheduler in SolarWinds (formerly Serv-U) FTP Voyager 16.2.0 allow remote attackers to hijack the authentication of users for requests that (1) change the admin password, (2) terminate the scheduler, or (3) possibly execute arbitrary commands via crafted requests to Admin/XML/Result.xml.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Solarwinds Ftp Voyager.

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

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

## Is CVE-2017-6803 being exploited?

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

Public exploit code:

- FTP Voyager Scheduler 16.2.0 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-25252](https://insights.sbomify.com/CVE-2018-25252/): FTP Voyager 16.2.0 Denial of Service via Malformed Site Profile (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6803 is a high-severity vulnerability in n/a, published on 20 Mar 2017. An attacker can exploit it over the internet without logging in, 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-6803 exists.

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

## Sources

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

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