Biscom Secure File Transfer versions 5.0.0.0 trough 5.1.1024 are vulnerable to post-authentication persistent cross-site scripting (XSS) in

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• biscom secure file transferup to 5.1.1015 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (rapid7). Independent of NVD's CPE analysis and usually ahead of it.

• Biscom Secure File Transfer

  • 5.0.0.0 trough 5.1.1024affected

Other highest-scoring records for the same primary product.

• CVE-2020-8796Biscom Secure File Transfer (SFT) before 5.1.1071 and 6.0.1xxx before 6.0.1005 allows Remote Code Execution on the server.
  40Plan
• CVE-2016-10710Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses sequential numbers, which allo
  32Monitor
• CVE-2020-27646Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft.
  26Monitor
• CVE-2020-8503Biscom 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
  26Monitor
• CVE-2017-5247Biscom Secure File Transfer is vulnerable to cross-site scripting in the File Name field.
  21Monitor
• CVE-2017-5246Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field.
  17Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1commentEl.innerHTML = comment.body;

1commentEl.textContent = comment.body;

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.