GHSA-7wmf-pw8j-mc78: Medium severity composer/codeigniter4/framework vulnerability
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.
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 to a fixed release to a version that resolves this vulnerability.
Fixed in 4.7.4 - Configuration
Configure the reverse proxy/load balancer to strip or overwrite client-supplied `X-Forwarded-Proto` and `Front-End-Https` headers before forwarding requests to the application.
Reverse proxy / load balancer Strip or overwrite client-supplied forwarding headers = Strip or overwrite X-Forwarded-Proto and Front-End-Https before forwarding to the application - Configuration
Adjust configuration so `IncomingRequest::isSecure()` does not trust client-supplied `X-Forwarded-Proto` and `Front-End-Https` headers from any incoming request.
CodeIgniter IncomingRequest::isSecure() Trust of X-Forwarded-Proto and Front-End-Https = Do not trust these headers from any incoming request - 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 GHSA-7wmf-pw8j-mc78?
The severity of GHSA-7wmf-pw8j-mc78 is rated as medium with a score of 4.8.
What impact does GHSA-7wmf-pw8j-mc78 have on applications?
GHSA-7wmf-pw8j-mc78 allows attackers to spoof headers, leading applications to incorrectly treat HTTP requests as secure.
How do I fix GHSA-7wmf-pw8j-mc78?
To mitigate GHSA-7wmf-pw8j-mc78, ensure that your application validates and processes the `X-Forwarded-Proto` and `Front-End-Https` headers securely.
Which software is affected by GHSA-7wmf-pw8j-mc78?
The vulnerability GHSA-7wmf-pw8j-mc78 affects the CodeIgniter4 framework.
When was GHSA-7wmf-pw8j-mc78 published?
GHSA-7wmf-pw8j-mc78 was published on August 7, 2026.