{"answers":{"affected":"2 open source packages ship an affected version, including statamic/cms.","exploited":"There is no known exploitation of CVE-2024-52600 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to 5.17.0 or later.","what":"CVE-2024-52600 is a medium-severity path traversal vulnerability in statamic cms, published on 19 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52600 and fix it if it is affected.\n\nWhat it is: CVE-2024-52600 is a medium-severity path traversal vulnerability in statamic cms, published on 19 Nov 2024. 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-2024-52600 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected all versions; fixed in 5.17.0\n- statamic/cms (Packagist): affected all versions; fixed in 5.17.0\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-2024-52600/ (Markdown: https://insights.sbomify.com/CVE-2024-52600/index.md)","id":"CVE-2024-52600","markdown":"https://insights.sbomify.com/CVE-2024-52600/index.md","name":"CVE-2024-52600","record":{"aliases":["GHSA-p7f6-8mcm-fwv3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"none","summary":"Attackers with upload permissions can use crafted filenames to place assets in unintended server locations, potentially overriding existing files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Statmatic is a Laravel and Git powered content management system (CMS). Prior to version 5.17.0, assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured. The issue affects front-end forms with `assets` fields and other places where assets can be uploaded, although users would need upload permissions anyway. Files can be uploaded so they would be located on the server in a different location, and potentially override existing files. Traversal outside an asset container is not possible. This path traversal vulnerability has been fixed in 5.17.0.","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":"Statamic CMS has Path Traversal in Asset Upload","id":"CVE-2024-52600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"iTop portal Insecure Direct Object Reference vulnerability","id":"CVE-2024-52601"},"packages":[{"ecosystem":"Packagist","fixed":["5.17.0"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-p7f6-8mcm-fwv3"},{"ecosystem":"Packagist","fixed":["5.17.0"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-p7f6-8mcm-fwv3"}],"prev":{"headline":"Tuleap vulnerable to XSS in the Gantt chart of the tracker plugin","id":"CVE-2024-52599"},"products":["cms"],"published":"2024-11-19","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-03","vendors":["statamic"]},"summary":"Attackers with upload permissions can use crafted filenames to place assets in unintended server locations, potentially overriding existing files.","url":"https://insights.sbomify.com/CVE-2024-52600/"}