GHSA-87pf-7x99-5xc4: Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers
In it's default configuration, SilverStripe trusts all originating IPs to include HTTP headers for Hostname, IP and Protocol. This enables reverse proxies to forward requests while still retaining the original request information. Trusted IPs can be limited via the SSTRUSTEDPROXYIPS constant. Even with this restriction in place, SilverStripe trusts a variety of HTTP headers due to different proxy notations (e.g.
Published May 23, 2024
Affected packages
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.0, <= 3.2.1
- Fixed in
- 3.2.2
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.0-beta1, < 3.3.0
- Fixed in
- 3.3.0
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- <= 3.1.16
- Fixed in
- 3.1.17
- Check
composer show silverstripe/framework
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
In it's default configuration, SilverStripe trusts all originating IPs to include HTTP headers for Hostname, IP and Protocol. This enables reverse proxies to forward requests while still retaining the original request information. Trusted IPs can be limited via the SS_TRUSTED_PROXY_IPS constant. Even with this restriction in place, SilverStripe trusts a variety of HTTP headers due to different proxy notations (e.g. X-Forwarded-For vs. Client-IP). Unless a proxy explicitly unsets invalid HTTP headers from connecting clients, this can lead to spoofing requests being passed through trusted proxies.
The impact of spoofed headers can include Director::forceSSL() not being enforced, SS_HTTPRequest->getIP() returning a wrong IP (disabling any IP restrictions), and spoofed hostnames circumventing any hostname-specific restrictions enforced in SilverStripe Controllers.
Regardless on running a reverse proxy in your hosting infrastructure, please follow the instructions on Secure Coding: Request hostname forgery in order to opt-in to these protections. If your website is not behind a reverse proxy, you might already be protected if using Apache with mod_env enabled, and you have the following line in your .htaccess file: SetEnv BlockUntrustedIPs true.
References
- https://github.com/silverstripe/silverstripe-framework/commit/37059eb6b3546f304e9c031abca0f096ddb175c6
- https://github.com/silverstripe/silverstripe-framework/commit/893e49703de4aa1855b5364919cbb0826f754fbf
- https://github.com/silverstripe/silverstripe-framework/commit/faa94d51d570788dcebc2f2ef6e9de4d179ce1e4
- https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-003-1.yaml
- https://www.silverstripe.org/download/security-releases/ss-2016-003
- https://github.com/advisories/GHSA-87pf-7x99-5xc4
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-88987
Silverstripe Framework: XSS via XHTML data URI
medium5.4Nov 16, 2026CVE-2026-88988
Silverstripe Framework: XSS via SVG data URI
medium5.4Nov 16, 2026CVE-2026-88989
Silverstripe Framework: Auth bypass GridFieldDetailForm
medium4.3Nov 16, 2026CVE-2026-91112
Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation
medium6.8Nov 16, 2026CVE-2026-91113
Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
medium4.3Nov 16, 2026CVE-2026-91115
Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
high8.8Nov 16, 2026
