CVE-2022-40832: CodeIgniter SQL Injection Vulnerability

codeigniter Updated 02 Oct 2025

Summary

31/01/2024
Yes i
Critical
Not published

CVE-2022-40832: B.C. Institute of Technology CodeIgniter. Affects codeigniter across 5 version ranges.

>= 3.0-rc.0, <= 3.0-rc.0 >= 3.0-rc2.0, <= 3.0-rc2.0 >= 3.0-rc3.0, <= 3.0-rc3.0 >= 3.0.0, < 3.1.13 >= 3.0.0, <= 3.0.0

Fixed in 3.1.13. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

CodeIgniter is an open-source PHP framework that provides a simple and elegant toolkit for building web applications. It is widely used for its lightweight nature, speed, and ease of use. However, versions up to 3.1.13 of CodeIgniter are vulnerable to SQL Injection attacks due to a flaw in the system/database/DB_query_builder.php file's having() function.

Vulnerability Detail

The SQL Injection vulnerability in CodeIgniter allows an attacker to manipulate SQL queries by injecting malicious input. This can lead to unauthorized access, data leakage, and potential remote code execution. The vulnerability arises from improper sanitization of user-supplied input in the having() function, which can be exploited to modify the structure and behavior of SQL queries.

How To Fix

Minimum fixed version

3.1.13

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, developers can manually sanitize and validate user input before using it in SQL queries. This can be done by using appropriate functions or libraries provided by CodeIgniter, such as the query builder class. Here is an example of how to use the query builder class to prevent SQL Injection:

$this->db->select('*');
$this->db->from('users');
$this->db->where('username', $this->db->escape($username));
$query = $this->db->get();

Conclusion

The SQL Injection vulnerability in CodeIgniter can have serious security implications, allowing attackers to manipulate SQL queries and potentially gain unauthorized access or execute arbitrary code. It is crucial for developers to upgrade to the latest version of CodeIgniter and implement proper input validation and parameterized queries to prevent SQL Injection attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for codeigniter →

Share this vulnerability

FAQ

CodeIgniter is an open-source PHP framework used for building web applications. It is known for its simplicity, speed, and ease of use.

SQL Injection is a type of security vulnerability that allows an attacker to manipulate SQL queries by injecting malicious input. This can lead to unauthorized access, data leakage, and potential remote code execution.

The SQL Injection vulnerability in CodeIgniter arises from improper sanitization of user-supplied input in the having() function of the system/database/DB_query_builder.php file. This allows an attacker to modify the structure and behavior of SQL queries.

The SQL Injection vulnerability in CodeIgniter can lead to unauthorized access, data leakage, and potential remote code execution. An attacker can manipulate SQL queries to extract sensitive information, modify or delete data, or even execute arbitrary code on the server.

The SQL Injection vulnerability in CodeIgniter can be mitigated by upgrading to version 3.1.14 or later, which includes a patch for the vulnerability. Developers should also review their codebase for any instances where user input is directly concatenated into SQL queries and implement proper input validation and parameterized queries to prevent SQL Injection attacks.

References

Related vulnerabilities

Recent vulnerabilities recorded for codeigniter.

How To Fix

Minimum fixed version

3.1.13

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback