CVE-2022-40829: CodeIgniter SQL Injection Vulnerability

codeigniter Updated 02 Oct 2025

Summary

31/01/2024
Yes i
Critical
Not published

CVE-2022-40829: 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

CodeIgniter is an open-source PHP web application framework that provides a simple and elegant toolkit for developers to build web applications. It is widely used for its lightweight nature, speed, and ease of use. However, versions up to 3.1.13 are vulnerable to SQL Injection attacks through the system\database\DB_query_builder.php or_like() function.

Vulnerability Detail

The SQL Injection vulnerability in CodeIgniter allows an attacker to manipulate SQL queries by injecting malicious SQL code. This can lead to unauthorized access, data leakage, and potential data modification or deletion. The vulnerability arises due to insufficient input validation and sanitization in the affected function, allowing an attacker to craft specially crafted input that can be executed as SQL commands.

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 prepared statements or parameterized queries to ensure that user input is treated as data and not executable code. Here is an example of using prepared statements in CodeIgniter:

$rawInput = $_POST['input'];

$sql = 'SELECT * FROM users WHERE username = ?';
$query = $this->db->query($sql, array($rawInput));
$result = $query->result();

Conclusion

The SQL Injection vulnerability in CodeIgniter can have severe consequences if left unaddressed. It is crucial for developers to upgrade to the latest version of CodeIgniter and implement proper input validation and sanitization techniques to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for codeigniter →

Share this vulnerability

FAQ

CodeIgniter is an open-source PHP web application framework that provides a simple and elegant toolkit for developers to build web applications.

SQL Injection is a web security vulnerability that allows an attacker to manipulate SQL queries by injecting malicious SQL code.

The potential consequences of this vulnerability include unauthorized access to sensitive data, data leakage, and potential data modification or deletion.

To fix this vulnerability, it is recommended to upgrade to CodeIgniter version 3.1.14 or later. Additionally, developers should ensure that user input is properly validated, sanitized, and parameterized before being used in SQL queries.

As a temporary workaround, developers can manually sanitize and validate user input before using it in SQL queries. This can be done by using prepared statements or parameterized queries.

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