Security readout for executives and security teams
Plain-English summary
Biscom Secure File Transfer had a stored cross-site scripting issue in file names. A logged-in user allowed to upload or send files could create a malicious file name that runs script when another logged-in user views it. Versions before 5.1.1028 are affected; 5.1.1028 is the stated fix version.
Executive priority
Prioritize remediation if Biscom SFT is internet-facing or broadly used by employees, customers, or partners. The issue is not listed as actively exploited in the supplied sources, but it can affect trusted users inside a file-transfer workflow.
Technical view
CVE-2017-5247 affects Biscom Secure File Transfer before 5.1.1028. The vulnerable field is File Name. The source states an authenticated user with upload or send permissions can include standard HTML scripting tags in a filename, and the script is evaluated for other authenticated users viewing that attacker-supplied filename.
Likely exposure
Exposure is limited to organizations running Biscom Secure File Transfer before 5.1.1028, especially where multiple authenticated users can upload, send, or view shared file listings.
Exploitation context
The bundle does not cite CISA KEV listing or confirmed active exploitation. The described attack requires authenticated access plus upload or send permissions, then another authenticated user viewing the crafted file name.
Researcher notes
The provided record has no CVSS, CWE, CPE, or detailed vendor remediation text beyond the affected range and fix version. Treat this as an authenticated stored XSS exposure and avoid assuming unauthenticated reachability or broader product impact.
Mitigation direction
- Upgrade Biscom Secure File Transfer to 5.1.1028 or later.
- Identify any deployments running versions before 5.1.1028.
- Limit upload and send permissions to trusted users until upgraded.
- Review Biscom guidance if an immediate upgrade is not possible.
Validation and detection
- Confirm the installed Biscom SFT version is 5.1.1028 or later.
- Review which authenticated roles can upload or send files.
- Inspect file listings for suspicious names containing HTML scripting tags.
- Verify file names render safely for authenticated viewers after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-5247 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://twitter.com/i_bo0om/status/885050741567750145CVE reference · x_refsource_MISC
- https://cve.biscom.com/bis-sft-cv-0005/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.