{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15080 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15080 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15080 is a medium-severity vulnerability in Prestashop Prestashop, published on 2 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15080 and fix it if it is affected.\n\nWhat it is: CVE-2020-15080 is a medium-severity vulnerability in Prestashop Prestashop, published on 2 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15080 in the wild and no public exploit code.\n\nAffected product: Prestashop Prestashop. 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-2020-15080/ (Markdown: https://insights.sbomify.com/CVE-2020-15080/index.md)","id":"CVE-2020-15080","markdown":"https://insights.sbomify.com/CVE-2020-15080/index.md","name":"CVE-2020-15080","record":{"aliases":["GHSA-492w-2pp5-xhvg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"E-commerce platform","requires_auth":"none","summary":"Attackers can access sensitive configuration files like composer.json and docker-compose.yml from the web server, potentially revealing infrastructure details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"prestashop","vendor":"prestashop"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In PrestaShop from version 1.7.4.0 and before version 1.7.6.6, some files should not be in the release archive, and others should not be accessible. The problem is fixed in version 1.7.6.6 A possible workaround is to make sure `composer.json` and `docker-compose.yml` are not accessible on your server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in release archive in PrestaShop","id":"CVE-2020-15080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"prestashop:prestashop","products":["prestashop:prestashop"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information exposure in the upload directory in PrestaShop","id":"CVE-2020-15081"},"packages":[],"prev":{"headline":"Improper access control in PrestaShop","id":"CVE-2020-15079"},"products":["PrestaShop"],"published":"2020-07-02","related":[{"cvss_score":10,"headline":"PrestaShop vulnerable to SQL filter bypass leading to arbitrary write requests using \"SQL Manager\"","id":"CVE-2023-30839","kev_date_added":null,"published":"2023-04-25"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2008-5791","kev_date_added":null,"published":"2008-12-31"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2024-41651","kev_date_added":null,"published":"2024-08-12"},{"cvss_score":9.8,"headline":"Remote code execution in prestashop","id":"CVE-2022-31181","kev_date_added":null,"published":"2022-08-01"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-3110","kev_date_added":null,"published":"2021-01-20"},{"cvss_score":9.8,"headline":"Blind SQL Injection in PrestaShop","id":"CVE-2020-15160","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2013-6295","kev_date_added":null,"published":"2020-02-18"}],"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-04","vendors":["PrestaShop"]},"summary":"Attackers can access sensitive configuration files like composer.json and docker-compose.yml from the web server, potentially revealing infrastructure details.","url":"https://insights.sbomify.com/CVE-2020-15080/"}