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

Security readout for executives and security teams

Biscom Secure File Transfer versions 5.0.1000 through 5.0.1048 allowed logged-in remote users to read or overwrite files because a request field was not properly validated. The published record says version 5.0.1050 fixed the issue. This matters most where Biscom SFT handles sensitive partner, customer, or regulated file exchanges. Exposure is limited to organizations running Biscom Secure File Transfer 5.0.1000 through 5.0.1048, especially internet-facing or partner-facing deployments with many authenticated users. Prioritize remediation if Biscom SFT is used for sensitive file exchange. The flaw affects confidentiality and integrity, and exploitation only requires authenticated access, which raises risk from compromised or overprivileged accounts. Mitigation focus: Upgrade affected Biscom SFT systems to version 5.0.1050 or later.; Check Biscom or vendor support guidance for any current supported upgrade path.; Restrict SFT access to required users and trusted network paths until upgraded..

Prepared

Jun 7, 2026, 20:58 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.