{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15285 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15285 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15285 is a high-severity vulnerability in n/a, published on 12 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-15285 and fix it if it is affected.\n\nWhat it is: CVE-2017-15285 is a high-severity vulnerability in n/a, published on 12 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-15285 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-15285/ (Markdown: https://insights.sbomify.com/CVE-2017-15285/index.md)","id":"CVE-2017-15285","markdown":"https://insights.sbomify.com/CVE-2017-15285/index.md","name":"CVE-2017-15285","record":{"aliases":["GHSA-m5fp-95pj-x2v6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"E-commerce platform","requires_auth":"low_privilege","summary":"Attackers with Vendor access can achieve remote code execution by uploading malicious PHP files via the product catalog attachment feature.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"x-cart","vendor":"qualiteam"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"X-Cart 5.2.23, 5.3.1.9, 5.3.2.13, and 5.3.3 is vulnerable to Remote Code Execution. This vulnerability exists because the application fails to check remote file extensions before saving locally. This vulnerability can be exploited by anyone with Vendor access or higher. One attack methodology is to upload an image file in the Attachments section of a product catalog, upload a .php file with an \"Add File Via URL\" action, and change the image's Description URL to reference the .php URL in the attachments/ directory.","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":"File upload in n/a","id":"CVE-2017-15285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-15286"},"packages":[],"prev":{"headline":"OctoberCMS Cross-Site Scripting","id":"CVE-2017-15284"},"products":["n/a"],"published":"2017-10-12","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2004-0241","kev_date_added":null,"published":"2004-03-18"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2006-2827","kev_date_added":null,"published":"2006-06-05"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2007-4907","kev_date_added":null,"published":"2007-09-17"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-4904","kev_date_added":null,"published":"2006-09-21"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-1822","kev_date_added":null,"published":"2005-06-01"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2015-0951","kev_date_added":null,"published":"2015-04-05"}],"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":["n/a"]},"summary":"Attackers with Vendor access can achieve remote code execution by uploading malicious PHP files via the product catalog attachment feature.","url":"https://insights.sbomify.com/CVE-2017-15285/"}