Search for packages
| purl | pkg:composer/silverstripe/cms@3.3.0-alpha |
| Tags | Ghost |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-agbu-v7vd-fyc8
Aliases: SS-2016-003 |
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 `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`. |
Affected by 7 other vulnerabilities. |
|
VCID-mr46-bvjx-n7ar
Aliases: SS-2015-028 |
Missing security check on dev/build/defaults The `buildDefaults` method on `DevelopmentAdmin` is missing a permission check. In live mode, if you access /dev/build, you are requested to login first. However, if you access /dev/build/defaults, then the action is performed without any login check. This should be protected in the same way that /dev/build is. The `buildDefaults` view is `requireDefaultRecords()` on each `DataObject` class, and hence has the potential to modify database state. It also lists all modified tables, allowing attackers more insight into which modules are used, and how the database tables are structured. |
Affected by 7 other vulnerabilities. |
|
VCID-qjey-bhrt-kud4
Aliases: SS-2016-002 |
CSRF vulnerability in GridFieldAddExistingAutocompleter GridField does not have sufficient CSRF protection, meaning that in some cases users with CMS access can be tricked into posting unspecified data into the CMS from external websites. Amongst other default CMS interfaces, GridField is used for management of groups, users and permissions in the CMS. |
Affected by 7 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2026-04-01T12:47:01.463757+00:00 | GitLab Importer | Affected by | VCID-mr46-bvjx-n7ar | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/silverstripe/cms/SS-2015-028.yml | 38.0.0 |
| 2026-04-01T12:47:01.432809+00:00 | GitLab Importer | Affected by | VCID-qjey-bhrt-kud4 | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/silverstripe/cms/SS-2016-002.yml | 38.0.0 |
| 2026-04-01T12:47:01.398052+00:00 | GitLab Importer | Affected by | VCID-agbu-v7vd-fyc8 | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/silverstripe/cms/SS-2016-003.yml | 38.0.0 |