{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5241 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5241 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5241 is a medium-severity cross-site scripting vulnerability in Biscom Secure File Transfer, published on 28 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-5241 and fix it if it is affected.\n\nWhat it is: CVE-2017-5241 is a medium-severity cross-site scripting vulnerability in Biscom Secure File Transfer, published on 28 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-5241 in the wild and no public exploit code.\n\nAffected product: Biscom Secure File Transfer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-5241/ (Markdown: https://insights.sbomify.com/CVE-2017-5241/index.md)","id":"CVE-2017-5241","markdown":"https://insights.sbomify.com/CVE-2017-5241/index.md","name":"CVE-2017-5241","record":{"aliases":["GHSA-qpgc-3j29-9h54"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure File Transfer","requires_auth":"low_privilege","summary":"Authenticated attackers can inject persistent scripts into workspace fields, potentially executing code or stealing sessions in Biscom Secure File Transfer.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"secure_file_transfer","vendor":"biscom"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in Secure File Transfer","id":"CVE-2017-5241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Rapid7 Nexpose Virtual Appliance Duplicate SSH Host Key","id":"CVE-2017-5242"},"packages":[],"prev":{"headline":"Memory corruption in AppSpider Pro","id":"CVE-2017-5240"},"products":["Secure File Transfer"],"published":"2017-06-28","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-8796","kev_date_added":null,"published":"2020-02-07"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2016-10710","kev_date_added":null,"published":"2018-01-25"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2020-27646","kev_date_added":null,"published":"2020-10-22"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-8503","kev_date_added":null,"published":"2020-01-31"},{"cvss_score":5.4,"headline":"Cross-site scripting in Secure File Transfer","id":"CVE-2017-5247","kev_date_added":null,"published":"2017-07-18"},{"cvss_score":4.3,"headline":"Cross-site scripting in Secure File Transfer","id":"CVE-2017-5246","kev_date_added":null,"published":"2017-07-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Biscom"]},"summary":"Authenticated attackers can inject persistent scripts into workspace fields, potentially executing code or stealing sessions in Biscom Secure File Transfer.","url":"https://insights.sbomify.com/CVE-2017-5241/"}