CodeIgniter vulnerabilities

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.

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.

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.

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.

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.

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.

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.