SilverStripe 3.1.6 Release Candidate 2

CPE Details

SilverStripe 3.1.6 Release Candidate 2
3.1.6
2020-02-21
19h18 +00:00
2020-02-21
19h18 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:silverstripe:silverstripe:3.1.6:rc2:*:*:*:*:*:*

Informations

Vendor

silverstripe

Product

silverstripe

Version

3.1.6

Update

rc2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2022-37421 2022-11-22 23h00 +00:00 Silverstripe silverstripe/cms through 4.11.0 allows XSS.
5.4
Medium
CVE-2022-28803 2022-06-28 22h50 +00:00 In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR).
5.4
Medium
CVE-2021-41559 2022-06-28 19h27 +00:00 Silverstripe silverstripe/framework 4.8.1 has a quadratic blowup in Convert::xml2array() that enables a remote attack via a crafted XML document.
6.5
Medium
CVE-2021-28661 2021-10-07 12h06 +00:00 Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.
4.3
Medium
CVE-2021-36150 2021-10-07 11h59 +00:00 SilverStripe Framework through 4.8.1 allows XSS.
6.1
Medium
CVE-2020-26136 2021-06-08 17h37 +00:00 In SilverStripe through 4.6.0-rc1, GraphQL doesn't honour MFA (multi-factor authentication) when using basic authentication.
6.5
Medium
CVE-2020-25817 2021-06-08 15h54 +00:00 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]).
4.8
Medium
CVE-2020-26138 2021-06-08 15h35 +00:00 In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation.
5.3
Medium
CVE-2020-9311 2020-07-15 19h00 +00:00 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.
5.4
Medium
CVE-2019-19326 2020-07-15 16h54 +00:00 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.
5.9
Medium
CVE-2019-12246 2020-02-19 15h29 +00:00 SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools.
4.3
Medium
CVE-2019-12437 2020-02-19 15h28 +00:00 In SilverStripe through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations,
8.8
High
CVE-2019-16409 2019-09-26 12h36 +00:00 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.)
5.3
Medium
CVE-2019-12617 2019-09-26 09h57 +00:00 In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.
2.7
Low
CVE-2019-14272 2019-09-26 09h50 +00:00 In SilverStripe asset-admin 4.0, there is XSS in file titles managed through the CMS.
5.4
Medium
CVE-2019-14273 2019-09-26 09h42 +00:00 In SilverStripe assets 4.0, there is broken access control on files.
5.3
Medium
CVE-2019-12205 2019-09-25 16h51 +00:00 SilverStripe through 4.3.3 has Flash Clipboard Reflected XSS.
6.1
Medium
CVE-2019-12203 2019-09-25 16h45 +00:00 SilverStripe through 4.3.3 allows session fixation in the "change password" form.
6.3
Medium
CVE-2019-12245 2019-09-25 16h41 +00:00 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.
5.3
Medium
CVE-2019-5715 2019-04-11 16h22 +00:00 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.
9.8
Critical
CVE-2017-18049 2018-01-23 05h00 +00:00 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.
5.5
Medium
CVE-2017-12849 2017-10-12 13h00 +00:00 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.
5.3
Medium
CVE-2017-14498 2017-09-15 16h00 +00:00 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.
6.1
Medium
CVE-2017-5197 2017-03-06 05h11 +00:00 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.
6.1
Medium
CVE-2015-8606 2016-04-13 13h00 +00:00 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.
6.1
Medium