CodeIgniter Query Builder SQL Injection in deleteBatch()

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CodeIgniter versions 4.3.0 through 4.7.3 contain a critical SQL injection vulnerability in the Query Builder's deleteBatch() method. The flaw occurs because bound parameter values from where() conditions are substituted into generated SQL without respecting their escape flags, allowing attackers to inject malicious SQL through user-controlled input. While the standard delete() method properly escapes bound parameters, the deleteBatch() code path bypasses these protections, creating a dangerous attack surface. This affects any application using CodeIgniter's Query Builder with user-supplied data in where conditions passed to deleteBatch(), potentially exposing database manipulation, data exfiltration, and unauthorized access across countless PHP-based web applications.

Casky's 322 mapped security skills leverage Claude's extended reasoning to detect the attack patterns associated with TA0001 (Initial Access) and TA0043 (Reconnaissance) techniques. Practitioners using Casky would identify suspicious SQL patterns in application logs, such as unexpected SQL metacharacters (semicolons, UNION operators, comment sequences) appearing in deleteBatch() query logs, combined with evidence of parameter binding anomalies. The platform's skills would flag requests where where() conditions contain SQL keywords or escape sequences that bypass normal input validation, correlate these with database activity showing unauthorized deletions or data access, and recognize the characteristic signature of bind parameter tampering. By analyzing the interaction between user input, parameter binding, and actual SQL execution, Casky helps teams pinpoint whether deleteBatch() calls are processing malicious payloads before they cause data loss.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-63221.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-63221

Casky has 322 skills that investigate the attack patterns behind CVE-2026-63221. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn