Advisory record · GHSA-c9w5-rwh3-7pm9

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

CVSS 9.4 CriticalCriticalEPSS 0.0061 · 49th percentile

Critical, because:

  • CVSS score 9.4: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 7 Aug 2026, 18:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
codeigniter4/frameworkPackagist>=4.3.0, <4.7.44.7.4
Identifiers
GHSA-c9w5-rwh3-7pm9 · CVE-2026-63221 · PKSA-t8h5-ngj8-z43w
Weakness (CWE)
CWE-89
Published
7 Aug 2026
Updated
7 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

CodeIgniter 4 (codeigniter4/framework) versions 4.3.0 up to but not including 4.7.4 are vulnerable to SQL injection in the Query Builder's deleteBatch() method when it is used with where() conditions. Where() bound values are inserted into the generated SQL without escaping, so an application that passes user-controlled input to where() before calling deleteBatch() lets an attacker run arbitrary SQL. Upgrade to version 4.7.4 or later; if that is not possible, avoid passing user-controlled input to where() with deleteBatch() and use delete() with binds for such conditions.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.4 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0061, the 49th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.