{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18176 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18176 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2018. 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-18176 and fix it if it is affected.\n\nWhat it is: CVE-2017-18176 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2018. 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-18176 in the wild and no public exploit code.\n\nAffected product: n/a. 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-18176/ (Markdown: https://insights.sbomify.com/CVE-2017-18176/index.md)","id":"CVE-2017-18176","markdown":"https://insights.sbomify.com/CVE-2017-18176/index.md","name":"CVE-2017-18176","record":{"aliases":["GHSA-wqvj-w8h2-pwwr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Sitefinity CMS","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in the context of the Sitefinity application by uploading malicious HTML files, potentially leading to session hijacking or data theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sitefinity","vendor":"progress"}],"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":"Progress Sitefinity 9.1 has XSS via file upload, because JavaScript code in an HTML file has the same origin as the application's own code. This is fixed in 10.1.","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 n/a","id":"CVE-2017-18176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-18177"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-18175"},"products":["n/a"],"published":"2018-02-12","related":[{"cvss_score":9.8,"headline":"Progress Telerik UI for ASP.NET AJAX and Sitefinity Cryptographic Weakness","id":"CVE-2017-9248","kev_date_added":"2021-11-03","published":"2017-07-03"},{"cvss_score":10,"headline":"CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity","id":"CVE-2026-7312","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":9.8,"headline":"CWE-284: Improper Access Control in web services in Progress Sitefinity","id":"CVE-2026-7198","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-29375","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-17392","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2017-15883","kev_date_added":null,"published":"2018-01-08"},{"cvss_score":8.8,"headline":"CWE-20: Improper Input Validation in web services in Progress Sitefinity","id":"CVE-2026-7195","kev_date_added":null,"published":"2026-06-02"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript in the context of the Sitefinity application by uploading malicious HTML files, potentially leading to session hijacking or data theft.","url":"https://insights.sbomify.com/CVE-2017-18176/"}