{"answers":{"affected":"2 open source packages ship an affected version, including codeigniter4/framework.","exploited":"There is no known exploitation of CVE-2026-63222 in the wild and no public exploit code.","fix":"Upgrade codeigniter4/framework to 4.7.4 or later.","what":"CVE-2026-63222 is a high-severity path traversal vulnerability in CodeIgniter4, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63222 and fix it if it is affected.\n\nWhat it is: CVE-2026-63222 is a high-severity path traversal vulnerability in CodeIgniter4, published on 31 Jul 2026. 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-2026-63222 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- codeigniter4/framework (Packagist): affected all versions; fixed in 4.7.4\n- codeigniter4/framework (Packagist): affected all versions; fixed in 4.7.4\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-2026-63222/ (Markdown: https://insights.sbomify.com/CVE-2026-63222/index.md)","id":"CVE-2026-63222","markdown":"https://insights.sbomify.com/CVE-2026-63222/index.md","name":"CVE-2026-63222","record":{"aliases":["GHSA-hhmc-q9hp-r662","UBUNTU-CVE-2026-63222"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP web framework","requires_auth":"none","summary":"Remote attackers can write files outside intended directories via path traversal in CodeIgniter's file upload handling.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.","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":"CodeIgniter: Path traversal in UploadedFile::move() when using client-provided filenames","id":"CVE-2026-63222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"CodeIgniter: Uploaded file extension validation bypass in is_image and mime_in rules","id":"CVE-2026-63223"},"packages":[{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["0"],"last_affected":[],"package":"codeigniter4/framework","purl":null,"source":"GHSA-hhmc-q9hp-r662"},{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["0"],"last_affected":[],"package":"codeigniter4/framework","purl":"pkg:composer/codeigniter4/framework","source":"GHSA-hhmc-q9hp-r662"}],"prev":{"headline":"CodeIgniter: SQL injection is possible via Query Builder deleteBatch() when used with where() conditions","id":"CVE-2026-63221"},"products":["CodeIgniter4"],"published":"2026-07-31","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":"2026-07-31","vendors":["codeigniter4"]},"summary":"Remote attackers can write files outside intended directories via path traversal in CodeIgniter's file upload handling.","url":"https://insights.sbomify.com/CVE-2026-63222/"}