CVE-2026-63223
CriticalCVSS 9.8Exploitation Probability (EPSS)
Elevated risk53th percentile - higher than 53% of all known CVEs
Summary
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.
Risk Assessment
An attacker can upload a PHP script and achieve remote code execution on the server, potentially leading to application compromise.
Recommendation
Update CodeIgniter to version 4.7.4 or later and add independent file extension validation (e.g., ext_in).
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-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-2026-48062Critical
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.
- 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.4, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. This issue is fixed in version 4.7.4.