{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-2210 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-2210 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2210 is a high-severity code injection vulnerability in n/a, published on 6 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-2210 and fix it if it is affected.\n\nWhat it is: CVE-2015-2210 is a high-severity code injection vulnerability in n/a, published on 6 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-2210 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-2015-2210/ (Markdown: https://insights.sbomify.com/CVE-2015-2210/index.md)","id":"CVE-2015-2210","markdown":"https://insights.sbomify.com/CVE-2015-2210/index.md","name":"CVE-2015-2210","record":{"aliases":["GHSA-cpw6-5jfx-2w4c"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Retail Store application","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code by injecting JavaScript into the help window to spawn a command shell.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crs_retail_store","vendor":"epicor"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"The help window in Epicor CRS Retail Store before 3.2.03.01.008 allows local users to execute arbitrary code by injecting Javascript into the window source to create a button that spawns a command shell.","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":"Code injection in n/a","id":"CVE-2015-2210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2015-2213"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2015-2209"},"products":["n/a"],"published":"2017-09-06","related":[],"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-06","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code by injecting JavaScript into the help window to spawn a command shell.","url":"https://insights.sbomify.com/CVE-2015-2210/"}