# CVE-2017-5247: Cross-site scripting in Secure File Transfer

> Authenticated attackers can inject scripts via file names, leading to code execution or account takeover for other users viewing the file.

- **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:** 18 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v4g7-jggm-2x5q

## What is CVE-2017-5247?

CVE-2017-5247 is a medium-severity cross-site scripting vulnerability in Biscom Secure File Transfer, published on 18 Jul 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

Biscom Secure File Transfer is vulnerable to cross-site scripting in the File Name field. An authenticated user with permissions to upload or send files can populate this field with a filename that contains standard HTML scripting tags. The resulting script will evaluated by any other authenticated user who views the attacker-supplied file name. All versions of SFT prior to 5.1.1028 are affected. The fix version is 5.1.1028.

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

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

It affects 1 product.


Products: Biscom Secure File Transfer.

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

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

## Is CVE-2017-5247 being exploited?

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

## Other vulnerabilities in Biscom Secure File Transfer

- [CVE-2020-8796](https://insights.sbomify.com/CVE-2020-8796/): Code injection in n/a (critical 9.8)
- [CVE-2016-10710](https://insights.sbomify.com/CVE-2016-10710/): Missing authorization in n/a (high 8.1)
- [CVE-2020-27646](https://insights.sbomify.com/CVE-2020-27646/): Information disclosure in n/a (medium 6.5)
- [CVE-2020-8503](https://insights.sbomify.com/CVE-2020-8503/): Missing authorization in n/a (medium 6.5)
- [CVE-2017-5241](https://insights.sbomify.com/CVE-2017-5241/): Cross-site scripting in Secure File Transfer (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5247 is a medium-severity cross-site scripting vulnerability in Biscom Secure File Transfer, published on 18 Jul 2017. 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-2017-5247 in the wild and no public exploit code.

Affected product: Biscom Secure File Transfer. 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-5247/ (Markdown: https://insights.sbomify.com/CVE-2017-5247/index.md)
```

## Sources

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

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