Injection in Biscom Secure File Transfer
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2017-5246
- 2026-10-03 Alias added: GHSA-687v-j3jj-3p7p
References
More Biscom Secure File Transfer vulnerabilities
- TI-2020-07055 Biscom Secure File Transfer (SFT) before 5.1.1071 and 6.0.1xxx before 6.0.1005 allows… CVSS 3.1CRITICAL 9.8
- TI-2016-08751 Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the… CVSS 3.0HIGH 8.1
- TI-2020-16762 Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft. CVSS 3.1MEDIUM 6.5
- TI-2020-06823 Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003… CVSS 3.1MEDIUM 6.5
- TI-2017-03352 Cross-site scripting in Biscom Secure File Transfer CVSS 3.0MEDIUM 5.4
- TI-2017-03357 Cross-site scripting in Biscom Secure File Transfer CVSS 3.0MEDIUM 5.4
Sources
- CVE-2017-5246 · CVE Program
- CVE-2017-5246 · NVD
- FIRST EPSS
- GHSA-687v-j3jj-3p7p · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences