{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-2922 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-2922 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-2922 is a medium-severity unsafe deserialization vulnerability in Pimcore Pimcore, published on 21 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-2922 and fix it if it is affected.\n\nWhat it is: CVE-2014-2922 is a medium-severity unsafe deserialization vulnerability in Pimcore Pimcore, published on 21 Apr 2014. 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-2014-2922 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-2014-2922/ (Markdown: https://insights.sbomify.com/CVE-2014-2922/index.md)","id":"CVE-2014-2922","markdown":"https://insights.sbomify.com/CVE-2014-2922/index.md","name":"CVE-2014-2922","record":{"aliases":["GHSA-63pp-7425-wfc8"],"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":"none","summary":"Remote attackers can exploit PHP object injection in Pimcore to delete arbitrary files and potentially execute code via unsafe deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pimcore","vendor":"pimcore"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The getObjectByToken function in Newsletter.php in the Pimcore_Tool_Newsletter module in pimcore 1.4.9 through 2.1.0 does not properly handle an object obtained by unserializing a pathname, which allows remote attackers to conduct PHP object injection attacks and delete arbitrary files via vectors involving a Zend_Http_Response_Stream object.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2014-10-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2014-10-12","kind":"exploitdb","ref":"43886","stars":null,"title":"Pimcore CMS 1.4.9 \u003c2.1.0 - Multiple Vulnerabilities"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Deserialization in n/a","id":"CVE-2014-2922","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"pimcore:pimcore","products":["pimcore:pimcore"],"type":"deserialization","year":"2014"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2014-2925"},"packages":[],"prev":{"headline":"Pimcore Vulnerable to PHP Object Injection Attacks","id":"CVE-2014-2921"},"products":["n/a"],"published":"2014-04-21","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":"Remote attackers can exploit PHP object injection in Pimcore to delete arbitrary files and potentially execute code via unsafe deserialization.","url":"https://insights.sbomify.com/CVE-2014-2922/"}