{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-14498 in the wild and no public exploit code.","fix":"Upgrade silverstripe/cms to 3.6.1 or later.","what":"CVE-2017-14498 is a medium-severity cross-site scripting vulnerability in Silverstripe Silverstripe, published on 15 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-14498 and fix it if it is affected.\n\nWhat it is: CVE-2017-14498 is a medium-severity cross-site scripting vulnerability in Silverstripe Silverstripe, published on 15 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-14498 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/cms (Packagist): affected all versions; fixed in 3.6.1\n- silverstripe/cms (Packagist): affected all versions; fixed in 3.6.1\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-14498/ (Markdown: https://insights.sbomify.com/CVE-2017-14498/index.md)","id":"CVE-2017-14498","markdown":"https://insights.sbomify.com/CVE-2017-14498/index.md","name":"CVE-2017-14498","record":{"aliases":["GHSA-j696-6m57-mcrv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Cross-site scripting vulnerability in SilverStripe CMS allows attackers to execute arbitrary scripts via malicious SVG uploads in the media editor.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/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":"SilverStripe CMS before 3.6.1 has XSS via an SVG document that is mishandled by (1) the Insert Media option in the content editor or (2) an admin/assets/add pathname, as demonstrated by the admin/pages/edit/EditorToolbar/MediaForm/field/AssetUploadField/upload URI, aka issue SS-2017-017.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Silverstripe CMS XSS Vulnerability","id":"CVE-2017-14498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"xss","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2017-14500"},"packages":[{"ecosystem":"Packagist","fixed":["3.6.1"],"introduced":["0"],"last_affected":[],"package":"silverstripe/cms","purl":null,"source":"GHSA-j696-6m57-mcrv"},{"ecosystem":"Packagist","fixed":["3.6.1"],"introduced":["0"],"last_affected":[],"package":"silverstripe/cms","purl":"pkg:composer/silverstripe/cms","source":"GHSA-j696-6m57-mcrv"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-14497"},"products":["n/a"],"published":"2017-09-15","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-2321","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":9.8,"headline":"Missing warning can lead to unauthenticated admin access in SilverStripe","id":"CVE-2019-12204","kev_date_added":null,"published":"2019-09-25"},{"cvss_score":9.8,"headline":"Silverstripe Framework SQLi Vulnerability","id":"CVE-2019-5715","kev_date_added":null,"published":"2019-04-11"},{"cvss_score":8.8,"headline":"Silverstripe CSRF Protection Bypass via GraphQL","id":"CVE-2019-12437","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":7.5,"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":7.5,"headline":"SilverStripe Folders migrated from 3.x may be unsafe to upload to","id":"CVE-2020-9280","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-4960","kev_date_added":null,"published":"2012-09-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["n/a"]},"summary":"Cross-site scripting vulnerability in SilverStripe CMS allows attackers to execute arbitrary scripts via malicious SVG uploads in the media editor.","url":"https://insights.sbomify.com/CVE-2017-14498/"}