{"answers":{"affected":"2 open source packages ship an affected version, including keystone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15881 in the wild and no public exploit code.","fix":"Upgrade keystone to 4.0.0-beta7 or later.","what":"CVE-2017-15881 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Oct 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-15881 and fix it if it is affected.\n\nWhat it is: CVE-2017-15881 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Oct 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-15881 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keystone (npm): affected all versions; fixed in 4.0.0-beta7\n- keystone (npm): affected all versions; fixed in 4.0.0-beta7\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-15881/ (Markdown: https://insights.sbomify.com/CVE-2017-15881/index.md)","id":"CVE-2017-15881","markdown":"https://insights.sbomify.com/CVE-2017-15881/index.md","name":"CVE-2017-15881","record":{"aliases":["GHSA-7cv6-gvx3-m54m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"KeystoneJS CMS","requires_auth":"high_privilege","summary":"Authenticated administrators can inject arbitrary scripts via content fields in KeystoneJS, potentially leading to code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"keystone","vendor":"keystonejs"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cross-Site Scripting vulnerability in KeystoneJS before 4.0.0-beta.7 allows remote authenticated administrators to inject arbitrary web script or HTML via the \"content brief\" or \"content extended\" field, a different vulnerability than CVE-2017-15878.","ecosystems":["npm"],"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":"Cross-Site Scripting in keystone","id":"CVE-2017-15881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-15882"},"packages":[{"ecosystem":"npm","fixed":["4.0.0-beta7"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":null,"source":"GHSA-7cv6-gvx3-m54m"},{"ecosystem":"npm","fixed":["4.0.0-beta7"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":"pkg:npm/keystone","source":"GHSA-7cv6-gvx3-m54m"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2017-15880"},"products":["n/a"],"published":"2017-10-24","related":[{"cvss_score":9.8,"headline":"NODE_ENV in Keystone defaults to development with esbuild","id":"CVE-2022-39382","kev_date_added":null,"published":"2022-11-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-29354","kev_date_added":null,"published":"2022-05-16"},{"cvss_score":9.1,"headline":"@keystone-6/core vulnerable to field-level access-control bypass for multiselect field","id":"CVE-2022-39322","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery (CSRF) in keystone","id":"CVE-2017-16570","kev_date_added":null,"published":"2017-11-06"},{"cvss_score":8.8,"headline":"Keystone is vulnerable to CSV injection","id":"CVE-2017-15879","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":7.5,"headline":"Authentication Weakness in keystone","id":"CVE-2015-9240","kev_date_added":null,"published":"2018-05-29"},{"cvss_score":7.1,"headline":"Cross-site Scripting (XSS) - Reflected in keystonejs/keystone","id":"CVE-2022-0087","kev_date_added":null,"published":"2022-01-11"}],"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":"Authenticated administrators can inject arbitrary scripts via content fields in KeystoneJS, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2017-15881/"}