GHSA-c9w5-rwh3-7pm9: SQL Injection
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.
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 to a fixed release to a version that resolves this vulnerability.
Fixed in v4.7.4 - Compensating control
If you cannot upgrade immediately, avoid passing user-controlled input into `where()` before calling `deleteBatch()`; instead use `delete()` with Query Builder binds for user-controlled conditions.
- Compensating control
When using `deleteBatch()` together with `where()` conditions, express required matching values through the batch data and `onConstraint()` rather than as separate user-controlled `where()` clauses.
- Compensating control
Strictly validate and cast values (e.g., numeric IDs) before using them in conditions; note this does not fully protect string conditions.
Event History
Frequently Asked Questions
What is the severity of GHSA-c9w5-rwh3-7pm9?
The severity of GHSA-c9w5-rwh3-7pm9 is rated as critical with a score of 9.4.
What type of vulnerability is GHSA-c9w5-rwh3-7pm9?
GHSA-c9w5-rwh3-7pm9 is a SQL injection vulnerability.
How do I fix GHSA-c9w5-rwh3-7pm9?
To fix GHSA-c9w5-rwh3-7pm9, update your CodeIgniter framework to the latest version where the issue is resolved.
What is the impact of GHSA-c9w5-rwh3-7pm9?
The impact of GHSA-c9w5-rwh3-7pm9 is that it can lead to unauthorized data access or corruption due to SQL injection.
When was GHSA-c9w5-rwh3-7pm9 published?
GHSA-c9w5-rwh3-7pm9 was published on August 7, 2026.