CVE-2026-63221

CodeIgniter: SQL injection in Query Builder deleteBatch() when used with where() conditions

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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-63221 has a CVSS score of 9.4 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.7.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Upgrade to v4.7.4 or later.

1. What is CVE-2026-63221? CVE-2026-63221 is a critical-severity SQL injection vulnerability in codeigniter4/framework (composer), affecting versions >= 4.3.0, < 4.7.4. It is fixed in 4.7.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-63221? CVE-2026-63221 has a CVSS score of 9.4 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of codeigniter4/framework are affected by CVE-2026-63221? codeigniter4/framework (composer) versions >= 4.3.0, < 4.7.4 is affected.
4. Is there a fix for CVE-2026-63221? Yes. CVE-2026-63221 is fixed in 4.7.4. Upgrade to this version or later.
5. Is CVE-2026-63221 exploitable, and should I be worried? Whether CVE-2026-63221 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-63221 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-63221? Upgrade codeigniter4/framework to 4.7.4 or later.

Other vulnerabilities in codeigniter4/framework