Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
89 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact The "Insert media from web" functionality in the CMS is vulnerable to XSS from a specially crafted embed. Reported by Jack Wallace from Bastion Security
Recommended action: Upgrade to 6.2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact User enumeration is possible by performing a timing attack on the login or password reset pages with user credentials. This was originally disclosed in https://www.silverstripe.org/download/security-releases/ss-2017-005/ for CMS 3 but was not patched in CMS 4+ References - https://www.silverstripe.org/download/security-releases/ss-2017-005 - https://www.silverstripe.org/download/security-releases/ss-2025-001
Recommended action: Upgrade to 5.3.23 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact A bad actor with access to edit content in the CMS could send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitised on the client-side, but server-side sanitisation doesn't catch it. The server-side sanitisation logic has been updated to sanitise against this attack. Reported by James Nicoll from Fujitsu Cyber References - https://www.silverstripe.org/download/security-releases/cve-2025-30148
Recommended action: Upgrade to 5.3.23 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
If a website has been set to the "dev" environment mode, a URL can be provided which includes an XSS payload which will be executed in the resulting error message.
Recommended action: Upgrade to 5.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
[!IMPORTANT] This vulnerability only affects sites which are in the "dev" environment mode. If your production website is in "dev" mode, it has been misconfigured, and you should immediately swap it to "live" mode. See https://docs.silverstripe.org/en/developerguides/debugging/environmenttypes/ for more information. If a website has been set to the "dev" environment mode, a URL can be provided which includes an XSS payload which will be executed in the resulting error message. References - https://www.silverstripe.org/download/security-releases/ss-2024-002 Reported by Gaurav Nayak from Chaleit
Recommended action: Upgrade to 5.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In some cases, form messages can contain HTML markup. This is an intentional feature, allowing links and other relevant HTML markup for the given message. Some form messages include content that the user can provide. There are scenarios in the CMS where that content doesn't get correctly sanitised prior to being included in the form message, resulting in an XSS vulnerability. References - https://www.silverstripe.org/download/security-releases/cve-2024-53277 Reported by Leo Diamat from Bastion Security Group
Recommended action: Upgrade to 5.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact When using the "insert media" functionality, the linked oEmbed JSON includes an HTML attribute which will replace the embed shortcode. The HTML is not sanitized before replacing the shortcode, allowing a script payload to be executed on both the CMS and the front-end of the website. References - https://www.silverstripe.org/download/security-releases/cve-2024-47605 Reported by James Nicoll from Fujitsu Cyber Security Services
Recommended action: Upgrade to 5.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact TinyMCE v6 has a configuration value convertunsafeembeds set to false which allows svg files containing javascript to be used in <object or <embed tags, which can be used as a vector for XSS attacks. Note that <embed tags are not allowed by default. After patching the default value of convertunsafeembeds will be set to true. This means that <object tags will be converted to iframes instead the next time the page is saved, which may break any pages that rely upon previously saved <object tags. Developers can override this configuration if desired to revert to the original behaviour. We reviewed the potential impact of this vulnerability within the context of Silverstripe CMS. We concluded this is a medium impact vulnerability given how TinyMCE is used by Silverstripe CMS. References: - https://www.silverstripe.org/download/security-releases/ss-2024-001 - https://github.com/advisories/GHSA-5359-pvf2-pw78
Recommended action: Upgrade to 5.2.16 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact A bad actor with access to edit content in the CMS could send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitised on the client-side, but server-side sanitisation doesn't catch it. The server-side sanitisation logic has been updated to sanitise against this type of attack. References - https://www.silverstripe.org/download/security-releases/cve-2024-32981
Recommended action: Upgrade to 5.2.16 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A potential SQL injection vulnerability was identified by using the silverstripe/postgresql database adapter. While unlikely to be exploitable, we have patched silverstripe/framework to ensure that table names are safely escaped before being passed to database adapters or user code.
Recommended action: Upgrade to 4.2.3, 4.1.4 or 4.0.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A possible denial of service attack vector has been identified in the dev/build system controller. dev/build now has its own URL token, similar to flushtoken, to ensure users are authenticated when running dev/build outside of dev environments.
Recommended action: Upgrade to 4.2.2, 4.1.3 or 4.0.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When running SilverStripe 3.7 or 4.x in dev mode with the mysqli database driver, there is a potential to disclose the connection details. We have blacklisted the sensitive parts of the connection information from being included in dev mode stack traces when database errors occur.
Recommended action: Upgrade to 4.2.2, 4.1.3, 4.0.5 or 3.7.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Some potentially dangerous file types exist in File.allowedextensions which could allow a malicious CMS user to upload files that then get executed in the security context of the website. We have removed the ability to upload .css, .js, .potm, .dotm, .xltm and .jar files in the default configuration. Since allowedextensions are synced to webserver configuration (in assets/.htaccess) automatically, this will also deny access to any existing uploads with these extensions. Review our security guidelines for the Common Web Platform and the File Security guide for SilverStripe 4 to find out how to add or remove extensions.
Recommended action: Upgrade to 4.1.1, 4.0.4 or 3.6.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
There is a user ID enumeration vulnerability in our brute force error messages. - Users that don't exist in will never get a locked out message - Users that do exist, will get a locked out message This means an attacker can infer or confirm user details that exist in the member table. This issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users. This is a regression of SS-2017-002.
Recommended action: Upgrade to 4.1.1 or 4.0.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Under some circumstances a form may populate a PasswordField with submitted data, reflecting submitted data back to a user. The user will only see their own submissions for password data, which is not considered best practice. We are not aware of data leaks to other users, devices or sessions.
Recommended action: Upgrade to 4.1.1, 4.0.4 or 3.7.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A weakness in the .htaccess rules preventing requests to uploaded PHP scripts allows PHP scripts that had made their way into the assets directory to be successfully executed through the use of a specially crafted URL. There are protections in place to disallow upload of PHP scripts through the CMS, meaning this weakness does not lead to direct vulnerabilities. In addition, sites hosted on the New Zealand Common Web Platform or SilverStripe Platform have additional configuration in place which prevents PHP script execution in assets, even in a malicious party manages to upload these into the folder.
Recommended action: Upgrade to 4.1.1 or 4.0.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
There is a vulnerability whereby arbitrary global functions may be executed if malicious user input is passed through to in the second argument of ViewableData::renderWith. This argument resolves associative arrays as template placeholders. This exploit requires that user code has been written which makes use of the second argument in renderWith and where user input is passed directly as a value in an associative array without sanitisation such as Convert::raw2xml(). ViewableData::customise is not vulnerable.
Recommended action: Upgrade to 4.1.1 or 4.0.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A carefully constructed malformed URL can be used to circumvent the offsite redirection protection used on BackURL parameters. This could lead to users entering sensitive data in malicious websites instead of the intended one.
Recommended action: Upgrade to 4.1.1 or 4.0.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When accessing the install.php script it is possible to extract any pre-configured database or default admin account password by viewing the source of the page, and inspecting the value property of the password fields.
Recommended action: Upgrade to 4.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A member with the permission EDITPERMISSIONS and access to the "Security" section is able to re-assign themselves (or another member) to ADMIN level. CMS Fields for the member are constructed using DirectGroups instead of Groups relation which results in bypassing security logic preventing privilege escalation.
Recommended action: Upgrade to 4.1.1, 4.0.4, 3.6.6 or 3.5.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The URL parameters isDev and isTest are accessible to unauthenticated users who access a SilverStripe website or application. This allows unauthorised users to expose information that is usually hidden on production environments such as verbose errors (including backtraces) and other debugging tools only available to sites running in "dev mode". Core functionality does not expose user data through these methods. Depending on your website configuration, community modules might have added more specific functionality which can be used to either access or alter user data. We have fixed the usage of isDev and isTest in SilverStripe 4.x, and removed the URL parameters in the next major release of SilverStripe.
Recommended action: Upgrade to 4.1.1 or 4.0.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When performing a fulltext search in SilverStripe 4.0.0 the 'start' querystring parameter is never escaped safely. This exposes a possible SQL injection vulnerability. The issue exists in 3.5 and 3.6 but is less vulnerable, as SearchForm sanitises these variables prior to passing to mysql.
Recommended action: Upgrade to 4.0.1, 3.6.3 or 3.5.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
All user login attempts are logged in the database in the LoginAttempt table. However, this table contains information in plain text, and may possible contain sensitive information, such as user passwords mis-typed into the username field. In order to address this a one-way hash is applied to the Email field before being stored.
Recommended action: Upgrade to 4.0.1, 3.6.3 or 3.5.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In the CSV export feature of the CMS it's possible for the output to contain macros and scripts, which if imported without sanitisation into software (including Microsoft Excel) may be executed. In order to safeguard against this threat all potentially executable cell values exported from CSV will be prepended with a literal tab character.
Recommended action: Upgrade to 4.0.1, 3.6.3 or 3.5.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
User enumeration is possible by performing a timing attack on the login or password reset pages with user credentials.
Recommended action: Upgrade to 3.6.2 or 3.5.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.