Filtered by vendor Silverstripe
Subscriptions
Filtered by product Silverstripe
Subscriptions
Total
64 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2013-2653 | 1 Silverstripe | 1 Silverstripe | 2022-10-03 | N/A |
| security/MemberLoginForm.php in SilverStripe 3.0.3 supports login using a GET request, which makes it easier for remote attackers to conduct phishing attacks without detection by the victim. | ||||
| CVE-2013-6789 | 1 Silverstripe | 1 Silverstripe | 2022-10-03 | N/A |
| security/MemberLoginForm.php in SilverStripe 3.0.3 supports credentials in a GET request, which allows remote or local attackers to obtain sensitive information by reading web-server access logs, web-server Referer logs, or the browser history, a similar vulnerability to CVE-2013-2653. | ||||
| CVE-2022-24444 | 1 Silverstripe | 1 Silverstripe | 2022-07-13 | 6.5 Medium |
| Silverstripe silverstripe/framework through 4.10 allows Session Fixation. | ||||
| CVE-2022-28803 | 1 Silverstripe | 1 Silverstripe | 2022-07-08 | 5.4 Medium |
| In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR). | ||||
| CVE-2021-28661 | 1 Silverstripe | 1 Silverstripe | 2021-10-15 | 4.3 Medium |
| Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass. | ||||
| CVE-2021-36150 | 1 Silverstripe | 1 Silverstripe | 2021-10-15 | 6.1 Medium |
| SilverStripe Framework through 4.8.1 allows XSS. | ||||
| CVE-2019-16409 | 2 Silverstripe, Symbiote | 2 Silverstripe, Versionedfiles | 2021-07-21 | 5.3 Medium |
| 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.) | ||||
| CVE-2020-6164 | 1 Silverstripe | 1 Silverstripe | 2021-07-21 | 7.5 High |
| 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). | ||||
| CVE-2020-25817 | 1 Silverstripe | 1 Silverstripe | 2021-06-17 | 4.8 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]). | ||||
| CVE-2020-26136 | 1 Silverstripe | 1 Silverstripe | 2021-06-16 | 6.5 Medium |
| In SilverStripe through 4.6.0-rc1, GraphQL doesn't honour MFA (multi-factor authentication) when using basic authentication. | ||||
| CVE-2020-26138 | 1 Silverstripe | 1 Silverstripe | 2021-06-16 | 5.3 Medium |
| In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation. | ||||
| CVE-2015-8606 | 1 Silverstripe | 1 Silverstripe | 2020-10-29 | N/A |
| 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. | ||||
| CVE-2019-12617 | 1 Silverstripe | 1 Silverstripe | 2020-08-24 | 2.7 Low |
| In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution. | ||||
| CVE-2019-12204 | 1 Silverstripe | 1 Silverstripe | 2020-08-24 | 9.8 Critical |
| In SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to unauthenticated admin access. | ||||
| CVE-2019-12245 | 1 Silverstripe | 1 Silverstripe | 2020-08-24 | 5.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. | ||||
| CVE-2019-19326 | 1 Silverstripe | 1 Silverstripe | 2020-07-23 | 5.9 Medium |
| 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. | ||||
| CVE-2020-6165 | 1 Silverstripe | 1 Silverstripe | 2020-07-23 | 5.3 Medium |
| 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. | ||||
| CVE-2020-9311 | 1 Silverstripe | 1 Silverstripe | 2020-07-22 | 5.4 Medium |
| 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. | ||||
| CVE-2020-9280 | 1 Silverstripe | 1 Silverstripe | 2020-04-29 | 7.5 High |
| 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. | ||||
| CVE-2019-19325 | 1 Silverstripe | 1 Silverstripe | 2020-02-20 | 6.1 Medium |
| 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. | ||||