p PatchFirst

PatchFirst · Latest vulnerabilities

silverstripe/framework vulnerabilities · Page 4

Vulnerabilities published for silverstripe/framework in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗ JSON ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 93

  1. CVE-2023-32302

    Low · CVSS 0Fix available

    Silverstripe Framework: Members with no password can be created and bypass custom login forms

    When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have so

    silverstripe/framework silverstripe/frameworkPHP
    • Update to 4.13.14
    • Update to 5.0.13
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  2. CVE-2023-22729

    Medium · CVSS 5.4EPSS 0.42%Fix available

    Silverstripe Framework has open redirect vulnerability on CMSSecurity relogin screen

    Silverstripe Framework is the Model-View-Controller framework that powers the Silverstripe content management system. Prior to version 4.12.15, an attacker can display a link to a third party website on a login screen by convincing a legitimate content author to follow a specially crafted link. Users should upgrade to Silverstripe Framework 4.12.15 or above to address the issue.

    silverstripe/frameworkPHP
    • Update to 4.12.5
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  3. CVE-2023-22728

    Medium · CVSS 4.3EPSS 0.49%Fix available

    Silverstripe Framework has missing permission check of canView in GridFieldPrintButton

    Silverstripe Framework is the Model-View-Controller framework that powers the Silverstripe content management system. Prior to version 4.12.15, the GridField print view incorrectly validates the permission of DataObjects potentially allowing a content author to view records they are not authorised to access. Users should upgrade to Silverstripe Framework 4.12.15 or above to address the issue.

    silverstripe/frameworkPHP
    • Update to 4.12.5
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  13. CVE-2020-25817

    Medium · CVSS 4.8EPSS 0.82%Fix available

    CVE-2020-25817

    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]).

    silverstripe/frameworkPHP
    • Update to 4.7.4
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  15. CVE-2020-9311

    Medium · CVSS 5.4EPSS 0.56%Fix available

    CVE-2020-9311

    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.

    silverstripe/frameworkPHP
    • Update to 3.7.5
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  16. CVE-2020-6164

    High · CVSS 7.5EPSS 1.8%Fix available

    CVE-2020-6164

    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).

    silverstripe/framework silverstripe/frameworkPHP
    • Update to 4.4.7
    • Update to 4.5.4
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  17. CVE-2019-19326

    Medium · CVSS 5.9EPSS 0.76%Fix available

    CVE-2019-19326

    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.

    silverstripe/framework silverstripe/framework silverstripe/frameworkPHP
    • Update to 3.7.5
    • Update to 4.4.7
    • Update to 4.5.4
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  18. CVE-2020-9280

    High · CVSS 7.5EPSS 1.73%Fix available

    CVE-2020-9280

    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.

    silverstripe/frameworkPHP
    • Update to 4.4.6
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  20. CVE-2019-19325

    Medium · CVSS 6.1EPSS 0.69%Fix available

    CVE-2019-19325

    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.

    silverstripe/framework silverstripe/frameworkPHP
    • Update to 4.4.5
    • Update to 4.5.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →