Filtered by vendor Silverstripe
Subscriptions
Total
85 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2019-12437 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 8.8 High |
In SilverStripe through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations, | ||||
CVE-2019-12246 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 4.3 Medium |
SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools. | ||||
CVE-2019-12245 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 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-12205 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 6.1 Medium |
SilverStripe through 4.3.3 has Flash Clipboard Reflected XSS. | ||||
CVE-2019-12204 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 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-12203 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 6.3 Medium |
SilverStripe through 4.3.3 allows session fixation in the "change password" form. | ||||
CVE-2019-12149 | 1 Silverstripe | 2 Registry, Restfulserver | 2024-11-21 | N/A |
SQL injection vulnerability in silverstripe/restfulserver module 1.0.x before 1.0.9, 2.0.x before 2.0.4, and 2.1.x before 2.1.2 and silverstripe/registry module 2.1.x before 2.1.1 and 2.2.x before 2.2.1 allows attackers to execute arbitrary SQL commands. | ||||
CVE-2017-5197 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
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. | ||||
CVE-2017-18049 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
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. | ||||
CVE-2017-14498 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
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. | ||||
CVE-2017-12849 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
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. | ||||
CVE-2015-8606 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 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-2015-5063 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe CMS & Framework 3.1.13 allow remote attackers to inject arbitrary web script or HTML via the (1) admin_username or (2) admin_password parameter to install.php. | ||||
CVE-2015-5062 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
Open redirect vulnerability in SilverStripe CMS & Framework 3.1.13 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the returnURL parameter to dev/build. | ||||
CVE-2013-6789 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 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-2013-2653 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | 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-2012-6458 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
Multiple cross-site scripting (XSS) vulnerabilities in the SilverStripe e-commerce module 3.0 for SilverStripe CMS allow remote attackers to inject arbitrary web script or HTML via the (1) FirstName, (2) Surname, or (3) Email parameter to code/forms/OrderFormAddress.php; or the (4) FirstName or (5) Surname parameter to code/forms/ShopAccountForm.php. | ||||
CVE-2012-4968 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe 2.3.x before 2.3.13 and 2.4.x before 2.4.7 allow remote attackers to inject arbitrary web script or HTML via (1) a crafted string to the AbsoluteLinks, (2) BigSummary, (3) ContextSummary, (4) EscapeXML, (5) FirstParagraph, (6) FirstSentence, (7) Initial, (8) LimitCharacters, (9) LimitSentences, (10) LimitWordCount, (11) LimitWordCountXML, (12) Lower, (13) LowerCase, (14) NoHTML, (15) Summary, (16) Upper, (17) UpperCase, or (18) URL method in a template, different vectors than CVE-2012-0976. | ||||
CVE-2012-0976 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
Cross-site scripting (XSS) vulnerability in admin/EditForm in SilverStripe 2.4.6 allows remote authenticated users with Content Authors privileges to inject arbitrary web script or HTML via the Title parameter. NOTE: some of these details are obtained from third party information. | ||||
CVE-2011-4962 | 1 Silverstripe | 1 Silverstripe | 2024-11-21 | N/A |
code/sitefeatures/PageCommentInterface.php in SilverStripe 2.4.x before 2.4.6 might allow remote attackers to execute arbitrary code via a crafted cookie in a user comment submission, which is not properly handled when it is deserialized. |