Biscom Secure File Transfer
7 CVEs affecting Biscom Secure File Transfer. Latest disclosed: 2020-10-22. Critical: 1, High: 1.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2020-8796 | Critical | 9.8 | 2020-02-07 | Biscom Secure File Transfer (SFT) before 5.1.1071 and 6.0.1xxx before 6.0.1005 allows Remote Code Execution on the server. |
CVE-2016-10710 | High | 8.1 | 2018-01-25 | 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 authentic… |
CVE-2020-27646 | Medium | 6.5 | 2020-10-22 | Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft. |
CVE-2020-8503 | Medium | 6.5 | 2020-01-31 | 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 se… |
CVE-2017-5247 | Medium | 5.4 | 2017-07-18 | 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 po… |
CVE-2017-5241 | Medium | 5.4 | 2017-06-28 | 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 "Des… |
CVE-2017-5246 | Medium | 4.3 | 2017-07-18 | Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a val… |