CVE-2017-5246

Description

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.

Category

4.3
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.28%
Third-Party Advisory twitter.com
Affected: Biscom Secure File Transfer
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2017-5246?
CVE-2017-5246 has been scored as a medium severity vulnerability.
How to fix CVE-2017-5246?
To fix CVE-2017-5246, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-5246 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-5246 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-5246?
CVE-2017-5246 affects Biscom Secure File Transfer.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.