CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 0CVE-2020-9311
https://notcve.org/view.php?id=CVE-2020-9311
In SilverStripe through 4.5, malicious users with a valid Silverstripe CMS login (usually CMS access) can craft profile information which can lead to XSS for other users through specially crafted login form URLs. En SilverStripe versiones hasta 4.5, los usuarios maliciosos con un inicio de sesión válido de Silverstripe CMS (generalmente acceso CMS) pueden crear información del perfil que puede conllevar a un ataque de tipo XSS para otros usuarios por medio de una URL de formulario de inicio de sesión especialmente diseñada • https://www.silverstripe.org/download/security-releases/CVE-2020-9311 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 8.8EPSS: 0%CPEs: 2EXPL: 0CVE-2020-9309
https://notcve.org/view.php?id=CVE-2020-9309
Silverstripe CMS through 4.5 can be susceptible to script execution from malicious upload contents under allowed file extensions (for example HTML code in a TXT file). When these files are stored as protected or draft files, the MIME detection can cause browsers to execute the file contents. Uploads stored as protected or draft files are allowed by default for authorised users only, but can also be enabled through custom logic as well as modules such as silverstripe/userforms. Sites using the previously optional silverstripe/mimevalidator module can configure MIME whitelists rather than extension whitelists, and hence prevent this issue. Sites on the Common Web Platform (CWP) use this module by default, and are not affected. • https://www.silverstripe.org/download/security-releases/CVE-2020-9309 • CWE-434: Unrestricted Upload of File with Dangerous Type •
CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0CVE-2020-6164
https://notcve.org/view.php?id=CVE-2020-6164
In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page). En SilverStripe versiones hasta 4.5.0, una ruta URL específica configurada por defecto por medio del módulo silverstripe/framework puede ser usada para revelar el hecho de que un dominio aloja una aplicación Silverstripe. • https://www.silverstripe.org/download/security-releases/CVE-2020-6164 •
CVSS: 5.3EPSS: 0%CPEs: 3EXPL: 0CVE-2020-6165
https://notcve.org/view.php?id=CVE-2020-6165
SilverStripe 4.5.0 allows attackers to read certain records that should not have been placed into a result set. This affects silverstripe/recipe-cms. The automatic permission-checking mechanism in the silverstripe/graphql module does not provide complete protection against lists that are limited (e.g., through pagination), resulting in records that should have failed a permission check being added to the final result set. GraphQL endpoints are configured by default (e.g., for assets), but the admin/graphql endpoint is access protected by default. This limits the vulnerability to all authenticated users, including those with limited permissions (e.g., where viewing records exposed through admin/graphql requires administrator permissions). • https://www.silverstripe.org/download/security-releases/CVE-2020-6165 • CWE-276: Incorrect Default Permissions •
CVSS: 5.9EPSS: 0%CPEs: 3EXPL: 0CVE-2019-19326
https://notcve.org/view.php?id=CVE-2019-19326
Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulnerable to web cache poisoning. Through modifying the X-Original-Url and X-HTTP-Method-Override headers, responses with malicious HTTP headers can return unexpected responses to other consumers of this cached response. Most other headers associated with web cache poisoning are already disabled through request hostname forgery whitelists. Los sitios de Silverstripe CMS versiones hasta 4.4.4 que han optado por Encabezados HTTP Cache en las respuestas atendidas por medio de la capa HTTP del framework pueden ser vulnerables al envenenamiento de la caché web. Mediante la modificación de los encabezados X-Original-Url y X-HTTP-Method-Override, las respuestas con encabezados HTTP maliciosos pueden devolver respuestas inesperadas a otros consumidores de esta respuesta almacenada en caché. • https://www.silverstripe.org/download/security-releases/CVE-2019-19326 • CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') •