CPE Details
SilverStripe 3.7.5
3.7.5
2020-08-06
11h09 +00:00
11h09 +00:00
2020-08-06
11h09 +00:00
11h09 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:silverstripe:silverstripe:3.7.5:*:*:*:*:*:*:*
Informations
Vendor
silverstripeProduct
silverstripeVersion
3.7.5Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| Silverstripe silverstripe/cms through 4.11.0 allows XSS. | 5.4 |
Medium |
||
| In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR). | 5.4 |
Medium |
||
| 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 |
||
| SilverStripe Framework through 4.8.1 allows XSS. | 6.1 |
Medium |
||
| In SilverStripe through 4.6.0-rc1, GraphQL doesn't honour MFA (multi-factor authentication) when using basic authentication. | 6.5 |
Medium |
||
| 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 |
||
| In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation. | 5.3 |
Medium |
||
| SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools. | 4.3 |
Medium |
||
| 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 |
||
| In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution. | 2.7 |
Low |
||
| In SilverStripe asset-admin 4.0, there is XSS in file titles managed through the CMS. | 5.4 |
Medium |
||
| In SilverStripe assets 4.0, there is broken access control on files. | 5.3 |
Medium |
||
| SilverStripe through 4.3.3 has Flash Clipboard Reflected XSS. | 6.1 |
Medium |
||
| SilverStripe through 4.3.3 allows session fixation in the "change password" form. | 6.3 |
Medium |
||
| 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 |
