{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8868 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8868 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8868 is a high-severity path traversal vulnerability in n/a, published on 10 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8868 and fix it if it is affected.\n\nWhat it is: CVE-2017-8868 is a high-severity path traversal vulnerability in n/a, published on 10 May 2017. 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-2017-8868 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-8868/ (Markdown: https://insights.sbomify.com/CVE-2017-8868/index.md)","id":"CVE-2017-8868","markdown":"https://insights.sbomify.com/CVE-2017-8868/index.md","name":"CVE-2017-8868","record":{"aliases":["GHSA-xq4m-r2r3-54jq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"flatCore CMS","requires_auth":"none","summary":"Attackers can delete arbitrary files via directory traversal in flatCore, potentially requiring CSRF interaction.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flatcore-cms","vendor":"flatcore"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"acp/core/files.browser.php in flatCore 1.4.7 allows file deletion via directory traversal in the delete parameter to acp/acp.php. The risk might be limited to requests submitted through CSRF.","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":"Path traversal in n/a","id":"CVE-2017-8868","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-8869"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2017-8867"},"products":["n/a"],"published":"2017-05-10","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2021-41403","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-7878","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2021-41402","kev_date_added":null,"published":"2022-06-16"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-7877","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":8,"headline":"Unrestricted Upload of File with Dangerous Type in flatcore/flatcore-cms","id":"CVE-2021-3745","kev_date_added":null,"published":"2021-10-28"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2017-7879","kev_date_added":null,"published":"2017-04-14"}],"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 can delete arbitrary files via directory traversal in flatCore, potentially requiring CSRF interaction.","url":"https://insights.sbomify.com/CVE-2017-8868/"}