Silverstripe

Silverstripe silverstripe/cms through 4.11.0 allows XSS.

Published: 2022-11-23T00:00:00.000Z
Updated: 2025-04-25T20:35:25.056Z

In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR).

Published: 2022-06-29T00:50:16.000Z
Updated: 2024-08-03T06:03:52.992Z

Silverstripe silverstripe/framework through 4.10 allows Session Fixation.

Published: 2022-06-28T21:30:54.000Z
Updated: 2024-08-03T04:13:55.612Z

Silverstripe silverstripe/framework 4.8.1 has a quadratic blowup in Convert::xml2array() that enables a remote attack via a crafted XML document.

Published: 2022-06-28T21:27:23.000Z
Updated: 2024-08-04T03:15:29.078Z

SilverStripe Framework through 4.8.1 allows XSS.

Published: 2021-10-07T13:59:08.000Z
Updated: 2024-08-04T00:47:43.850Z

Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.

Published: 2021-10-07T14:06:31.000Z
Updated: 2024-08-03T21:47:32.974Z

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.

Published: 2020-07-15T21:00:17.000Z
Updated: 2024-08-04T10:26:15.990Z

In SilverStripe through 4.5, files uploaded via Forms to folders migrated from Silverstripe CMS 3.x may be put to the default "/Uploads" folder instead. This affects installations which allowed upload folder protection via the optional silverstripe/secureassets module under 3.x. This module is installed and enabled by default on the Common Web Platform (CWP). The vulnerability only affects files uploaded after an upgrade to 4.x.

Published: 2020-04-15T20:18:14.000Z
Updated: 2024-08-04T10:26:15.922Z

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). However, if custom GraphQL endpoints have been configured for a specific implementation (usually under /graphql), this vulnerability could also be exploited through unauthenticated requests. This vulnerability only applies to reading records; it does not allow unauthorised changing of records.

Published: 2020-07-15T20:27:39.000Z
Updated: 2024-08-04T08:55:21.935Z

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).

Published: 2020-07-15T20:32:16.000Z
Updated: 2024-08-04T08:55:21.841Z

In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation.

Published: 2021-06-08T17:35:06.000Z
Updated: 2024-08-04T15:49:07.142Z

In SilverStripe through 4.6.0-rc1, GraphQL doesn't honour MFA (multi-factor authentication) when using basic authentication.

Published: 2021-06-08T19:37:45.000Z
Updated: 2024-08-04T15:49:07.106Z

SilverStripe through 4.6.0-rc1 has an XXE Vulnerability in CSSContentParser. A developer utility meant for parsing HTML within unit tests can be vulnerable to XML External Entity (XXE) attacks. When this developer utility is misused for purposes involving external or user submitted data in custom project code, it can lead to vulnerabilities such as XSS on HTML output rendered through this custom code. This is now mitigated by disabling external entities during parsing. (The correct CVE ID year is 2020 [CVE-2020-25817, not CVE-2021-25817]).

Published: 2021-06-08T17:54:01.000Z
Updated: 2024-08-04T15:40:36.948Z

All versions of SilverStripe 3 prior to 3.6.7 and 3.7.3, and all versions of SilverStripe 4 prior to 4.0.7, 4.1.5, 4.2.4, and 4.3.1 allows Reflected SQL Injection through Form and DataObject.

Published: 2019-04-11T18:22:52.000Z
Updated: 2024-08-04T20:01:52.221Z

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.

Published: 2020-07-15T18:54:55.000Z
Updated: 2024-08-05T02:16:46.998Z

SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user's credentials or other sensitive user input.

Published: 2020-02-17T19:59:29.000Z
Updated: 2024-08-05T02:16:46.824Z

In the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)

Published: 2019-09-26T14:36:27.000Z
Updated: 2024-08-05T01:17:39.578Z

In SilverStripe assets 4.0, there is broken access control on files.

Published: 2019-09-26T11:42:49.000Z
Updated: 2024-08-05T00:12:43.341Z

In SilverStripe asset-admin 4.0, there is XSS in file titles managed through the CMS.

Published: 2019-09-26T11:50:53.000Z
Updated: 2024-08-05T00:12:43.351Z

In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.

Published: 2019-09-26T11:57:18.000Z
Updated: 2024-08-04T23:24:39.204Z

In SilverStripe through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations,

Published: 2020-02-19T16:28:06.000Z
Updated: 2024-08-04T23:17:40.140Z

SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools.

Published: 2020-02-19T16:29:37.000Z
Updated: 2024-08-04T23:17:38.907Z

SilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.

Published: 2019-09-25T18:41:07.000Z
Updated: 2024-08-04T23:17:38.201Z

SilverStripe through 4.3.3 has Flash Clipboard Reflected XSS.

Published: 2019-09-25T18:51:31.000Z
Updated: 2024-08-04T23:17:38.219Z

In SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to unauthenticated admin access.

Published: 2019-09-25T18:25:06.000Z
Updated: 2024-08-04T23:17:38.108Z

SilverStripe through 4.3.3 allows session fixation in the "change password" form.

Published: 2019-09-25T18:45:44.000Z
Updated: 2024-08-04T23:17:38.116Z

There is XSS in SilverStripe CMS before 3.4.4 and 3.5.x before 3.5.2. The attack vector is a page name. An example payload is a crafted JavaScript event handler within a malformed SVG element.

Published: 2017-03-06T06:11:00.000Z
Updated: 2024-08-05T14:55:35.615Z

In the CSV export feature of SilverStripe before 3.5.6, 3.6.x before 3.6.3, and 4.x before 4.0.1, it's possible for the output to contain macros and scripts, which may be executed if imported without sanitization into common software (including Microsoft Excel). For example, the CSV data may contain untrusted user input from the "First Name" field of a user's /myprofile page.

Published: 2018-01-23T06:00:00.000Z
Updated: 2024-08-05T21:06:50.219Z

SilverStripe CMS before 3.6.1 has XSS via an SVG document that is mishandled by (1) the Insert Media option in the content editor or (2) an admin/assets/add pathname, as demonstrated by the admin/pages/edit/EditorToolbar/MediaForm/field/AssetUploadField/upload URI, aka issue SS-2017-017.

Published: 2017-09-15T18:00:00.000Z
Updated: 2024-08-05T19:27:40.642Z

Response discrepancy in the login and password reset forms in SilverStripe CMS before 3.5.5 and 3.6.x before 3.6.1 allows remote attackers to enumerate users via timing attacks.

Published: 2017-10-12T15:00:00.000Z
Updated: 2024-08-05T18:51:06.384Z

Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe CMS & Framework before 3.1.16 and 3.2.x before 3.2.1 allow remote attackers to inject arbitrary web script or HTML via the (1) Locale or (2) FailedLoginCount parameter to admin/security/EditForm/field/Members/item/new/ItemEditForm.

Published: 2016-04-13T15:00:00.000Z
Updated: 2024-08-06T08:20:43.475Z

Cross-site scripting (XSS) vulnerability in the process function in SSViewer.php in SilverStripe before 2.3.13 and 2.4.x before 2.4.6 allows remote attackers to inject arbitrary web script or HTML via the QUERY_STRING to template placeholders, as demonstrated by a request to (1) admin/reports/, (2) admin/comments/, (3) admin/, (4) admin/show/, (5) admin/assets/, and (6) admin/security/.

Published: 2014-04-08T14:00:00.000Z
Updated: 2024-08-07T00:23:39.120Z

SilverStripe before 2.4.2 allows remote authenticated users to change administrator passwords via vectors related to admin/security.

Published: 2012-08-26T18:00:00.000Z
Updated: 2024-09-17T02:32:34.578Z

SilverStripe before 2.4.2 does not properly restrict access to pages in draft mode, which allows remote attackers to obtain sensitive information.

Published: 2012-08-26T18:00:00.000Z
Updated: 2024-09-16T18:19:25.429Z

Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe before 2.3.5 allow remote attackers to inject arbitrary web script or HTML via (1) the CommenterURL parameter to PostCommentForm, and in the Forum module before 0.2.5 in SilverStripe before 2.3.5 allow remote attackers to inject arbitrary web script or HTML via (2) the Search parameter to forums/search (aka the search script).

Published: 2010-04-28T23:00:00.000Z
Updated: 2024-08-07T01:28:41.998Z

SQL injection vulnerability in SilverStripe before 2.2.2 allows remote attackers to execute arbitrary SQL commands via unspecified vectors related to AjaxUniqueTextField.

Published: 2009-04-27T17:43:00.000Z
Updated: 2024-08-07T11:42:00.445Z