{"answers":{"affected":"2 open source packages ship an affected version, including craftcms/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3814 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3814 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3814 is a high-severity vulnerability in Craftcms Craft Cms, published on 1 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3814 and fix it if it is affected.\n\nWhat it is: CVE-2018-3814 is a high-severity vulnerability in Craftcms Craft Cms, published on 1 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3814 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- craftcms/cms (Packagist): affected all versions up to 2.6.3000; no fix listed\n- craftcms/cms (Packagist): affected all versions up to 2.6.3000; no fix listed\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-2018-3814/ (Markdown: https://insights.sbomify.com/CVE-2018-3814/index.md)","id":"CVE-2018-3814","markdown":"https://insights.sbomify.com/CVE-2018-3814/index.md","name":"CVE-2018-3814","record":{"aliases":["GHSA-r342-vjc4-wrmj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Craft CMS","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary PHP code by uploading a malicious file disguised as an image and renaming it via the asset replacement feature.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"craft_cms","vendor":"craftcms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Craft CMS 2.6.3000 allows remote attackers to execute arbitrary PHP code by using the \"Assets-\u003eUpload files\" screen and then the \"Replace it\" option, because this allows a .jpg file to have embedded PHP code, and then be renamed to a .php extension.","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":false,"headline":"Craft CMS PHP Code Injection Vulnerability","id":"CVE-2018-3814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"craftcms:craft_cms","products":["craftcms:craft_cms"],"type":"file_upload","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-3815"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.6.3000"],"package":"craftcms/cms","purl":null,"source":"GHSA-r342-vjc4-wrmj"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.6.3000"],"package":"craftcms/cms","purl":"pkg:composer/craftcms/cms","source":"GHSA-r342-vjc4-wrmj"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-3813"},"products":["n/a"],"published":"2018-01-01","related":[{"cvss_score":10,"headline":"Craft CMS Code Injection","id":"CVE-2025-32432","kev_date_added":"2026-03-20","published":"2025-04-25"},{"cvss_score":9.3,"headline":"Craft CMS Code Injection","id":"CVE-2024-56145","kev_date_added":"2025-06-02","published":"2024-12-18"},{"cvss_score":8.1,"headline":"Craft CMS Code Injection","id":"CVE-2025-23209","kev_date_added":"2025-02-20","published":"2025-01-18"},{"cvss_score":6.9,"headline":"Craft CMS External Control of Assumed-Immutable Web Parameter","id":"CVE-2025-35939","kev_date_added":"2025-06-02","published":"2025-05-07"},{"cvss_score":10,"headline":"Craft CMS Remote Code Execution vulnerability","id":"CVE-2023-41892","kev_date_added":null,"published":"2023-09-13"},{"cvss_score":9.8,"headline":"Craft CMS Remote Code Injection","id":"CVE-2021-27903","kev_date_added":null,"published":"2021-06-30"},{"cvss_score":9.8,"headline":"SEOmatic for CraftCMS allows Server-Side Template Injection","id":"CVE-2020-9757","kev_date_added":null,"published":"2020-03-04"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary PHP code by uploading a malicious file disguised as an image and renaming it via the asset replacement feature.","url":"https://insights.sbomify.com/CVE-2018-3814/"}