CVE-2026-63221: CodeIgniter: SQL injection in Query Builder deleteBatch() when used with where() conditions
Impact A SQL injection vulnerability exists in the Query Builder's deleteBatch() method. When deleteBatch() is used together with where() conditions, the bound values from the WHERE clause are substituted directly into the generated SQL with their escape flag ignored, so they are never escaped or quoted. If an application passes user-controlled input to where() before calling deleteBatch(), that input is interpreted as SQL rather than as a value, allowing SQL injection.
This affects only the deleteBatch() code path. Regular delete() operations escape where() binds correctly.
Patches Upgrade to v4.7.4 or later.
Workarounds If you cannot upgrade immediately:
- Strictly validate and cast values (e.g. numeric IDs) before using them in conditions - though this does not fully protect string conditions. - Do not pass user-controlled input to where() when using deleteBatch(). - For user-controlled conditions, use a normal delete() with Query Builder binds instead of deleteBatch(). - Where possible, express required matching values through the batch data and onConstraint() rather than as separate user-controlled where() clauses.
Other sources
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.
— MITRE
CodeIgniter: SQL injection in Query Builder deleteBatch() when used with where() conditions
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/codeigniter4/frameworkto a version that resolves this vulnerability.Fixed in 4.7.4 - Upgrade
Upgrade
CodeIgniterto a version that resolves this vulnerability.Fixed in 4.7.4 - Compensating control
Until upgrading, do not pass user-controlled input to where() when using deleteBatch(); use a normal delete() with Query Builder binds instead. Strictly validate and cast values, such as numeric IDs, before using them in conditions, and where possible express required matching values through the batch data and onConstraint() rather than separate user-controlled where() clauses.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63221?
CVE-2026-63221 has a critical severity level of 9.4.
How does CVE-2026-63221 affect CodeIgniter?
CVE-2026-63221 allows SQL injection via Query Builder deleteBatch() when used with unsafe where() conditions.
What versions of CodeIgniter are impacted by CVE-2026-63221?
CodeIgniter versions 4.3.0 through 4.7.3 are affected by CVE-2026-63221.
How do I fix CVE-2026-63221?
To fix CVE-2026-63221, upgrade to CodeIgniter version 4.7.4 or later.
What type of vulnerability is CVE-2026-63221 classified as?
CVE-2026-63221 is classified as an SQL Injection vulnerability.