Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2016-10710: Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses

50
This month
HIGH 8.1UPGRADE

CVE-2016-10710 is a high-severity flaw (CVSS 8.1) 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 (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses sequential numbers, which allows remote authenticated users to overwrite or read files via crafted requests. Version 5.0.1050 contains the fix.

Why this priority

  • High severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-20
Published2018-01-25
Last modified2026-06-17
Publisher (CNA): MITRE · 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.0.1000 and <= 5.0.1048
Fixed in: newer than 5.0.1048
Safe to downgrade to: a release before 5.0.1000
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.0.1048 (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.
3. If no update is available yet, DOWNGRADE to a release before 5.0.1000 (Debian / Ubuntu)
apt-cache madison secure-file-transfer sudo apt install secure-file-transfer=<VERSION_BEFORE_5.0.1000> sudo apt-mark hold secure-file-transfer
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list secure-file-transfer sudo dnf downgrade secure-file-transfer-<VERSION_BEFORE_5.0.1000> sudo dnf versionlock add secure-file-transfer
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2016-10710?

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

Is CVE-2016-10710 being exploited?

CVE-2016-10710 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-2016-10710 affect?

CVE-2016-10710 affects secure file transfer. Severity is high (CVSS 8.1). Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses sequential numbers, which allows remote authenticated users to overwrite or read files via crafted requests. Version 5.0.1050 cont

How urgent is CVE-2016-10710?

Priority 50/100. High severity; 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.