{"answers":{"affected":"2 open source packages ship an affected version, including october/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5296 in the wild and no public exploit code.","fix":"Upgrade october/cms to 1.0.466 or later.","what":"CVE-2020-5296 is a medium-severity path traversal vulnerability in Octobercms October, published on 3 Jun 2020. 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-2020-5296 and fix it if it is affected.\n\nWhat it is: CVE-2020-5296 is a medium-severity path traversal vulnerability in Octobercms October, published on 3 Jun 2020. 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-2020-5296 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- october/cms (Packagist): affected from 1.0.319; fixed in 1.0.466\n- october/cms (Packagist): affected from 1.0.319; fixed in 1.0.466\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-5296/ (Markdown: https://insights.sbomify.com/CVE-2020-5296/index.md)","id":"CVE-2020-5296","markdown":"https://insights.sbomify.com/CVE-2020-5296/index.md","name":"CVE-2020-5296","record":{"aliases":["GHSA-jv6v-fvvx-4932"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OctoberCMS","requires_auth":"high_privilege","summary":"Authenticated backend users with asset management permissions can delete arbitrary local files on the OctoberCMS server.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"october","vendor":"octobercms"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-610","name":"Externally Controlled Reference to a Resource in Another Sphere"},{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"In OctoberCMS (october/october composer package) versions from 1.0.319 and before 1.0.466, an attacker can exploit this vulnerability to delete arbitrary local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission. Issue has been patched in Build 466 (v1.0.466).","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":"Arbitrary File Deletion vulnerability in OctoberCMS","id":"CVE-2020-5296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"octobercms:october","products":["octobercms:october"],"type":"path_traversal","year":"2020"},"n_packages":2,"n_references":4,"next":{"headline":"Upload whitelisted files to any directory in OctoberCMS","id":"CVE-2020-5297"},"packages":[{"ecosystem":"Packagist","fixed":["1.0.466"],"introduced":["1.0.319"],"last_affected":[],"package":"october/cms","purl":null,"source":"GHSA-jv6v-fvvx-4932"},{"ecosystem":"Packagist","fixed":["1.0.466"],"introduced":["1.0.319"],"last_affected":[],"package":"october/cms","purl":"pkg:composer/october/cms","source":"GHSA-jv6v-fvvx-4932"}],"prev":{"headline":"Local File read vulnerability in OctoberCMS","id":"CVE-2020-5295"},"products":["october"],"published":"2020-06-03","related":[{"cvss_score":8.2,"headline":"October CMS Improper Authentication","id":"CVE-2021-32648","kev_date_added":"2022-01-18","published":"2021-08-26"},{"cvss_score":9.8,"headline":"October CMS Session ID not invalidated after logout","id":"CVE-2021-3311","kev_date_added":null,"published":"2021-02-05"},{"cvss_score":9.8,"headline":"October CMS File Upload Vulnerability","id":"CVE-2017-1000194","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2017-1000196","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2017-1000197","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.1,"headline":"October CMS safe mode bypass using Twig sandbox escape","id":"CVE-2023-44382","kev_date_added":null,"published":"2023-12-01"},{"cvss_score":8.8,"headline":"Authenticated file write leads to remote code execution in october/system","id":"CVE-2021-32649","kev_date_added":null,"published":"2022-01-14"}],"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-04","vendors":["octobercms"]},"summary":"Authenticated backend users with asset management permissions can delete arbitrary local files on the OctoberCMS server.","url":"https://insights.sbomify.com/CVE-2020-5296/"}