Filtered by vendor Silverstripe
Subscriptions
Filtered by product Framework
Subscriptions
Total
13 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2024-47605 | 1 Silverstripe | 2 Asset Admin, Framework | 2025-07-12 | 5.4 Medium |
silverstripe-asset-admin is a silverstripe assets gallery for asset management. When using the "insert media" functionality, the linked oEmbed JSON includes an HTML attribute which will replace the embed shortcode. The HTML is not sanitized before replacing the shortcode, allowing a script payload to be executed on both the CMS and the front-end of the website. This issue has been addressed in silverstripe/framework version 5.3.8 and users are advised to upgrade. There are no known workarounds for this vulnerability. | ||||
CVE-2023-48714 | 1 Silverstripe | 1 Framework | 2025-06-17 | 4.3 Medium |
Silverstripe Framework is the framework that forms the base of the Silverstripe content management system. Prior to versions 4.13.39 and 5.1.11, if a user should not be able to see a record, but that record can be added to a `GridField` using the `GridFieldAddExistingAutocompleter` component, the record's title can be accessed by that user. Versions 4.13.39 and 5.1.11 contain a fix for this issue. | ||||
CVE-2022-38148 | 1 Silverstripe | 1 Framework | 2025-04-30 | 8.8 High |
Silverstripe silverstripe/framework through 4.11 allows SQL Injection. | ||||
CVE-2022-38146 | 1 Silverstripe | 1 Framework | 2025-04-30 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11 allows XSS (issue 2 of 3). | ||||
CVE-2022-38724 | 1 Silverstripe | 3 Asset Admin, Assets, Framework | 2025-04-29 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11.0, silverstripe/assets through 1.11.0, and silverstripe/asset-admin through 1.11.0 allow XSS. | ||||
CVE-2022-38462 | 1 Silverstripe | 1 Framework | 2025-04-29 | 6.1 Medium |
Silverstripe silverstripe/framework through 4.11 is vulnerable to XSS by carefully crafting a return URL on a /dev/build or /Security/login request. | ||||
CVE-2022-38147 | 1 Silverstripe | 1 Framework | 2025-04-25 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11 allows XSS (issue 3 of 3). | ||||
CVE-2022-38145 | 1 Silverstripe | 1 Framework | 2025-04-25 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11 allows XSS (issue 1 of 3) via remote attackers adding a Javascript payload to a page's meta description and get it executed in the versioned history compare view. | ||||
CVE-2022-37430 | 1 Silverstripe | 1 Framework | 2025-04-25 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11 allows XSS vulnerability via href attribute of a link (issue 2 of 2). | ||||
CVE-2022-37429 | 1 Silverstripe | 1 Framework | 2025-04-25 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.11 allows XSS (issue 1 of 2) via JavaScript payload to the href attribute of a link by splitting a javascript URL with white space characters. | ||||
CVE-2023-22728 | 1 Silverstripe | 1 Framework | 2025-01-31 | 4.3 Medium |
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. | ||||
CVE-2023-22729 | 1 Silverstripe | 1 Framework | 2025-01-31 | 5.4 Medium |
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. | ||||
CVE-2022-25238 | 1 Silverstripe | 1 Framework | 2024-11-21 | 5.4 Medium |
Silverstripe silverstripe/framework through 4.10.0 allows XSS, inside of script tags that can can be added to website content via XHR by an authenticated CMS user if the cwp-core module is not installed on the sanitise_server_side contig is not set to true in project code. |
Page 1 of 1.