Silverstripe: >> Silverstripe >> 3.0.2 Security Vulnerabilities
Silverstripe silverstripe/cms through 4.11.0 allows XSS.
CVSS Score
5.4
EPSS Score
0.003
Published
2022-11-23
In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR).
CVSS Score
5.4
EPSS Score
0.01
Published
2022-06-29
Silverstripe silverstripe/framework 4.8.1 has a quadratic blowup in Convert::xml2array() that enables a remote attack via a crafted XML document.
CVSS Score
6.5
EPSS Score
0.003
Published
2022-06-28
Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.
CVSS Score
4.3
EPSS Score
0.002
Published
2021-10-07
SilverStripe Framework through 4.8.1 allows XSS.
CVSS Score
6.1
EPSS Score
0.005
Published
2021-10-07
In SilverStripe through 4.6.0-rc1, GraphQL doesn't honour MFA (multi-factor authentication) when using basic authentication.
CVSS Score
6.5
EPSS Score
0.002
Published
2021-06-08
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]).
CVSS Score
4.8
EPSS Score
0.003
Published
2021-06-08
In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation.
CVSS Score
5.3
EPSS Score
0.003
Published
2021-06-08
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.
CVSS Score
5.4
EPSS Score
0.003
Published
2020-07-15
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.
CVSS Score
5.9
EPSS Score
0.002
Published
2020-07-15
Page 1