{"answers":{"affected":"2 open source packages ship an affected version, including codeigniter4/framework.","exploited":"There is no known exploitation of CVE-2026-63221 in the wild and no public exploit code.","fix":"Upgrade codeigniter4/framework to 4.7.4 or later.","what":"CVE-2026-63221 is a critical SQL injection 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-63221 and fix it if it is affected.\n\nWhat it is: CVE-2026-63221 is a critical SQL injection 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-63221 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- codeigniter4/framework (Packagist): affected from 4.3.0; fixed in 4.7.4\n- codeigniter4/framework (Packagist): affected from 4.3.0; 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-63221/ (Markdown: https://insights.sbomify.com/CVE-2026-63221/index.md)","id":"CVE-2026-63221","markdown":"https://insights.sbomify.com/CVE-2026-63221/index.md","name":"CVE-2026-63221","record":{"aliases":["GHSA-c9w5-rwh3-7pm9","UBUNTU-CVE-2026-63221"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP web framework","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the deleteBatch method in CodeIgniter, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"CodeIgniter is a PHP full-stack web framework. From 4.3.0 through 4.7.3, Query Builder deleteBatch() substitutes bound values from where() conditions into generated SQL while ignoring their escape flags, allowing user-controlled condition values to be interpreted as SQL. This affects only the deleteBatch() code path. Regular delete() operations escape where() binds correctly. 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: SQL injection is possible via Query Builder deleteBatch() when used with where() conditions","id":"CVE-2026-63221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"CodeIgniter: Path traversal in UploadedFile::move() when using client-provided filenames","id":"CVE-2026-63222"},"packages":[{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["4.3.0"],"last_affected":[],"package":"codeigniter4/framework","purl":null,"source":"GHSA-c9w5-rwh3-7pm9"},{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["4.3.0"],"last_affected":[],"package":"codeigniter4/framework","purl":"pkg:composer/codeigniter4/framework","source":"GHSA-c9w5-rwh3-7pm9"}],"prev":{"headline":"CodeIgniter: Spoofable forwarded HTTPS headers in IncomingRequest::isSecure()","id":"CVE-2026-63220"},"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":"Attackers can execute arbitrary SQL commands via the deleteBatch method in CodeIgniter, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2026-63221/"}