Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-5241: Biscom Secure File Transfer versions 5.0.0.0 trough 5.1.1024 are vulnerable to post-authentication persistent

39
Routine
MEDIUM 5.4UPGRADE

CVE-2017-5241 is a medium-severity flaw (CVSS 5.4) affecting secure file transfer. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score5.4 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance0.9% (top 41%)
CISA exploited listNo
WeaknessCWE-79
Published2017-06-28
Last modified2026-06-17
Publisher (CNA): Rapid7, Inc. · Vendor: biscom

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

biscom secure file transfer UPGRADE
Affected: <= 5.1.1015
Fixed in: newer than 5.1.1015
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy secure-file-transfer || rpm -q secure-file-transfer || secure-file-transfer --version
2. UPGRADE to newer than 5.1.1015 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade secure-file-transfer
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade secure-file-transfer
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-5241?

secure file transfer: upgrade to newer than 5.1.1015. Exact commands for each OS are on this page.

Is CVE-2017-5241 being exploited?

CVE-2017-5241 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-5241 affect?

CVE-2017-5241 affects secure file transfer. Severity is medium (CVSS 5.4). 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 Det

How urgent is CVE-2017-5241?

Priority 39/100. Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.