Biscom develops a focused secure file transfer product serving a prominent role in regulated data-exchange workflows, where the vendor's disclosures cluster around input-handling and authorization weaknesses. Vulnerabilities affecting the vendor skew toward serious outcomes, with an elevated share reaching critical severity, and recur through weakness classes including cross-site scripting, authorization bypass, improper input validation, and injection-style flaws that reflect the complexity of web-based file transfer and access control. Current severity and exploitation counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Biscom over time
Signals from CVEs in this vendor scope (7 CVEs).
7 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-8796CRITICAL Biscom Secure File Transfer (SFT) before 5.1.1071 and 6.0.1xxx before 6.0.1005 allows Remote Code Execution on the server. | Feb 7, 2020 | 9.8 | 32 | NO | NO |
CVE-2016-10710HIGH 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 overwri | Jan 25, 2018 | 8.1 | 25 | NO | NO |
CVE-2020-27646MEDIUM Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft. | Oct 22, 2020 | 6.5 | 21 | NO | NO |
CVE-2020-8503MEDIUM Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003 allows Insecure Direct Object Reference (IDOR) by an authenticated sender because of an er | Jan 31, 2020 | 6.5 | 21 | NO | NO |
CVE-2017-5241MEDIUM 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 | Jun 28, 2017 | 5.4 | 21 | NO | NO |
CVE-2017-5247MEDIUM 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 wit | Jul 18, 2017 | 5.4 | 15 | NO | NO |
CVE-2017-5246MEDIUM Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expressi | Jul 18, 2017 | 4.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (7 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Biscom.
Media articles that mention a CVE ID that affects a product developed by Biscom — matched by CVE ID, not by vendor name.