CVE-2026-63220: CodeIgniter: Spoofable forwarded HTTPS headers in IncomingRequest::isSecure()
Impact IncomingRequest::isSecure() trusted the X-Forwarded-Proto and Front-End-Https headers from any incoming request. In affected deployments, an attacker could spoof these headers and cause the application to incorrectly treat an HTTP request as secure.
This may impact applications that rely on isSecure(), forcehttps(), 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.
Patches Upgrade to v4.7.4 or later.
Workarounds Users who cannot upgrade immediately should enforce HTTP-to-HTTPS redirects outside CodeIgniter, for example with Apache .htaccess/virtual host rules, nginx server blocks, Caddy site config, or load balancer redirect rules.
Users should also ensure that reverse proxies strip or overwrite client-supplied X-Forwarded-Proto and Front-End-Https headers before forwarding requests to the application.
Other sources
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(), forcehttps(), 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.
— MITRE
CodeIgniter: Spoofable forwarded HTTPS headers in IncomingRequest::isSecure()
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/codeigniter4/frameworkto a version that resolves this vulnerability.Fixed in 4.7.4 - Upgrade
Upgrade
CodeIgniterto a version that resolves this vulnerability.Fixed in 4.7.4 - Configuration
Configure the reverse proxy/load balancer to strip or overwrite any incoming client-supplied `X-Forwarded-Proto` and `Front-End-Https` headers before the request reaches CodeIgniter.
Reverse proxy/load balancer Strip/overwrite client-supplied headers = X-Forwarded-Proto and Front-End-Https should be stripped or overwritten before forwarding - Compensating control
If you cannot upgrade immediately, enforce HTTP-to-HTTPS redirects outside CodeIgniter (e.g., Apache `.htaccess`/virtual host rules, nginx server blocks, Caddy site config, or load balancer redirect rules).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63220?
CVE-2026-63220 has a medium severity rating of 4.8.
How do I fix CVE-2026-63220?
To fix CVE-2026-63220, update CodeIgniter to version 4.7.4 or later.
What is the risk associated with CVE-2026-63220?
The risk associated with CVE-2026-63220 is that attackers can spoof forwarded HTTPS headers.
What versions of CodeIgniter are affected by CVE-2026-63220?
CodeIgniter versions prior to 4.7.4 are affected by CVE-2026-63220.
What is the nature of the vulnerability in CVE-2026-63220?
CVE-2026-63220 allows the application to incorrectly treat HTTP requests as secure due to trusted spoofed headers.