CVE-2026-63220
MediumCVSS 4.8Exploitation Probability (EPSS)
Low risk3th percentile - higher than 3% of all known CVEs
Summary
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.
Risk Assessment
Applications relying on isSecure() or force_https() could be deceived, leading to confidentiality breaches of data transmitted over HTTP.
Recommendation
Update CodeIgniter to version 4.7.4 or later. Configure the reverse proxy to strip or overwrite client-supplied forwarding headers.
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-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.
Original NVD description (English source)
CodeIgniter is a PHP full-stack web framework. In versions prior to 4.7.4, IncomingRequest::isSecure() trusted the X-Forwarded-Proto and Front-End-Https headers from any incoming request, allowing an attacker could spoof these headers and cause the application to incorrectly treat an HTTP request as secure. This may have impacted applications that rely on isSecure(), force_https(), forceGlobalSecureRequests, or similar logic to enforce HTTPS-only access or make security-sensitive decisions. Exploitability depends on deployment configuration. Applications are most exposed if the backend is reachable directly over HTTP, or if a reverse proxy/load balancer forwards client-supplied forwarding headers without stripping or overwriting them. This issue has been fixed in version 4.7.4.