CVE-2026-48062
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk36th percentile - higher than 36% of all known CVEs
Summary
CodeIgniter before version 4.7.3 contains a vulnerability in the ext_in validation rule, which checks the extension based on the detected MIME type rather than the actual file extension. A file named shell.php with GIF content can pass validation, potentially leading to arbitrary code execution.
Risk Assessment
An attacker can upload a PHP file disguised as an image, which when saved on the server can be executed, leading to remote code execution and server compromise.
Recommendation
Update CodeIgniter to version 4.7.3 or later.
Other vulnerabilities in CodeIgniter
See all- CVE-2017-1000247High
CodeIgniter version 3.1.3, used by the British Columbia Institute of Technology, is vulnerable to HTTP Header Injection in the set_status_header() function under Apache, leading to HTTP Header Injection flaws.
- CVE-2026-63223Critical
CodeIgniter prior to 4.7.4 has a vulnerability in the is_image and mime_in upload validation rules that do not enforce a safe client filename extension. A remote attacker can upload executable content if the application preserves the client filename and stores uploads in a web-accessible script-enabled directory.
- CVE-2026-63221Critical
CodeIgniter from 4.3.0 through 4.7.3 has a vulnerability in the Query Builder deleteBatch() method that substitutes bound values from where() conditions into generated SQL while ignoring their escape flags, allowing SQL injection.
- CVE-2014-8686Critical
CodeIgniter before 2.2.0 makes it easier for attackers to decode session cookies by leveraging fallback to a custom XOR-based encryption scheme when the Mcrypt extension for PHP is not available.
- CVE-2026-63222High
CodeIgniter prior to version 4.7.4 is vulnerable in the UploadedFile::move() method. Calling it without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory.
- CVE-2026-63220Medium
In CodeIgniter before version 4.7.4, IncomingRequest::isSecure() trusts X-Forwarded-Proto and Front-End-Https headers, allowing an attacker to spoof them and cause the application to incorrectly treat an HTTP request as secure, potentially affecting HTTPS enforcement logic.
Original NVD description (English source)
CodeIgniter is a PHP full-stack web framework. Prior to 4.7.3, the ext_in upload validation rule in system/Validation/StrictRules/FileRules.php checked the MIME-derived guessed extension instead of the client-provided filename extension. As a result, an uploaded file named shell.php containing GIF-like content could pass validation such as uploaded[avatar]|is_image[avatar]|mime_in[avatar,image/gif]|ext_in[avatar,gif] because the detected MIME type maps to gif, even though the uploaded filename extension is php. Applications are impacted if they accept user-controlled uploads, rely on ext_in to validate the uploaded filename extension, save uploaded files using the original client filename with $file->move($path), store uploads in a web-accessible directory, and allow PHP or other executable files to run from that directory. In those conditions, this may lead to arbitrary code execution. This issue is fixed in version 4.7.3.