Biscom

biscom

7 CVEs • 1 product

Products (1)

Click to collapse

Toggle

Secure File Transfer

secure_file_transfer

CVEs (7)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2020-27646 1Biscom 1Secure File Transfer Jun 17, 2026 Oct 22, 2020 N/A· v4 6.5 MEDIUM· v3 4.3 MEDIUM· v2 Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft.
CVE-2020-8796 1Biscom 1Secure File Transfer Jun 17, 2026 Feb 7, 2020 N/A· v4 9.8 CRITICAL· v3 7.5 HIGH· v2 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-2020-8503 1Biscom 1Secure File Transfer Jun 17, 2026 Jan 31, 2020 N/A· v4 6.5 MEDIUM· v3 3.5 LOW· v2 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 error in a file-upload feature. This is fi...Show more 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 error in a file-upload feature. This is fixed in 5.1.1068 and 6.0.1004.Show less
CVE-2016-10710 1Biscom 1Secure File Transfer Nov 21, 2024 Jan 25, 2018 N/A· v4 8.1 HIGH· v3 6.5 MEDIUM· v2 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. V...Show more 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.Show less
CVE-2017-5247 1Biscom 1Secure File Transfer May 13, 2026 Jul 18, 2017 N/A· v4 5.4 MEDIUM· v3 3.5 LOW· v2 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 with a filename that contains standard HTML...Show more 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 with a filename that contains standard HTML scripting tags. The resulting script will evaluated by any other authenticated user who views the attacker-supplied file name. All versions of SFT prior to 5.1.1028 are affected. The fix version is 5.1.1028.Show less
CVE-2017-5246 1Biscom 1Secure File Transfer May 13, 2026 Jul 18, 2017 N/A· v4 4.3 MEDIUM· v3 4.0 MEDIUM· v2 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 expression, wrapped in double curly-braces ({{ }...Show more 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 expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker's display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028.Show less
CVE-2017-5241 1Biscom 1Secure File Transfer May 13, 2026 Jun 28, 2017 N/A· v4 5.4 MEDIUM· v3 3.5 LOW· v2 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"...Show more 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.Show less