Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/codeigniter4/CodeIgniter4/commit/ecbf044666bed41d23f07518096d
- https://github.com/codeigniter4/CodeIgniter4/releases/tag/v4.7.4
- https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-7wmf-pw8j-
FAQ
What is CVE-2026-63220?
CVE-2026-63220 is a vulnerability with a CVSS score of 4.8 (MEDIUM). 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 ...
How severe is CVE-2026-63220?
CVE-2026-63220 has been rated MEDIUM with a CVSS base score of 4.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-63220?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.