{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-4425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-4425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-4425 is a medium-severity path traversal vulnerability in Pimcore Pimcore, published on 18 Aug 2015. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-4425 and fix it if it is affected.\n\nWhat it is: CVE-2015-4425 is a medium-severity path traversal vulnerability in Pimcore Pimcore, published on 18 Aug 2015. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-4425 in the wild and no public exploit code.\n\nAffected product: Pimcore Pimcore. 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-2015-4425/ (Markdown: https://insights.sbomify.com/CVE-2015-4425/index.md)","id":"CVE-2015-4425","markdown":"https://insights.sbomify.com/CVE-2015-4425/index.md","name":"CVE-2015-4425","record":{"aliases":["GHSA-9f4f-4qr3-8cr7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pimcore CMS","requires_auth":"low_privilege","summary":"Authenticated users with asset permissions can write arbitrary files via path traversal, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pimcore","vendor":"pimcore"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:S/C:N/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Directory traversal vulnerability in pimcore before build 3473 allows remote authenticated users with the \"assets\" permission to create or write to arbitrary files via a .. (dot dot) in the dir parameter to admin/asset/add-asset-compatibility.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-07-14","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-07-14","kind":"exploitdb","ref":"37609","stars":null,"title":"Pimcore CMS Build 3450 - Directory Traversal"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2015-4425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"pimcore:pimcore","products":["pimcore:pimcore"],"type":"path_traversal","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2015-4426"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2015-4422"},"products":["n/a"],"published":"2015-08-18","related":[{"cvss_score":9.8,"headline":"RCE vulnerability in Pimcore/Mail \u0026 Dynamic Text Layout","id":"CVE-2022-39365","kev_date_added":null,"published":"2022-10-27"},{"cvss_score":9.8,"headline":"Pimcore Access Control Issues","id":"CVE-2019-18981","kev_date_added":null,"published":"2019-11-15"},{"cvss_score":9.8,"headline":"Pimcore 2FA Vulnerable to Brute Forcing","id":"CVE-2019-18985","kev_date_added":null,"published":"2019-11-15"},{"cvss_score":8.8,"headline":"Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848","id":"CVE-2026-23492","kev_date_added":null,"published":"2026-01-14"},{"cvss_score":8.8,"headline":"SQL Injection in Admin Grid Filter API in Pimcore","id":"CVE-2023-47637","kev_date_added":null,"published":"2023-11-15"},{"cvss_score":8.8,"headline":"Pimcore SQL Injection Vulnerability in Admin Search Find API","id":"CVE-2023-30848","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":8.8,"headline":"Pimcore vulnerable to SQL Injection in Translation Export API","id":"CVE-2023-30849","kev_date_added":null,"published":"2023-04-27"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated users with asset permissions can write arbitrary files via path traversal, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2015-4425/"}