Silverstripe Framework
Approved changes feed: RSS · Atom
cpe:2.3:a:silverstripe:silverstripe-framework:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Silverstripe (fb3ee4e6-70c4-5017-82a7-81441bb33bd1) |
|---|---|
| Product | Silverstripe Framework (9a77a2bc-39e1-54fc-a902-918ffd93e13c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54720 |
vulnerable | 2026-07-29 01:00:27.936303 |
Silverstripe Framework: Possible XSS attack through media embed
MEDIUM (5.4)
Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. In versions prior to 6.2.2, the "Insert media from web" functionality in the CMS is vulnerable to XSS from a specially crafted embed. This issue was fixed in version 6.2.2/
Published: 2026-07-01T21:02:59.522Z
Updated: 2026-07-02T15:54:49.241Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-30148 |
vulnerable | 2026-06-08 07:16:59.124048 |
Silverstripe Framework has a XSS vulnerability in HTML editor
MEDIUM (5.4)
Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 5.3.23, bad actor with access to edit content in the CMS could send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitized on the client-side, but server-side sanitization doesn't catch it. The server-side sanitization logic has been updated to sanitize against this attack. This vulnerability is fixed in 5.3.23.
Published: 2025-04-10T13:02:22.415Z
Updated: 2025-04-10T13:34:14.930Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-53277 |
vulnerable | 2026-06-08 06:54:14.900593 |
Cross-site Scripting in form messages in silverstripe framework
MEDIUM (5.4)
Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. In some cases, form messages can contain HTML markup. This is an intentional feature, allowing links and other relevant HTML markup for the given message. Some form messages include content that the user can provide. There are scenarios in the CMS where that content doesn't get correctly sanitised prior to being included in the form message, resulting in an XSS vulnerability. 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.
Published: 2025-01-14T22:45:07.403Z
Updated: 2025-01-15T14:52:21.490Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32981 |
vulnerable | 2026-06-08 06:37:24.842138 |
Cross-site Scripting vulnerability with encoded payload in silverstripe/framework
MEDIUM (5.4)
Silverstripe framework is the PHP framework forming the base for the Silverstripe CMS. In affected versions a bad actor with access to edit content in the CMS could add send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitised on the client-side, but server-side sanitisation doesn't catch it. The server-side sanitisation logic has been updated to sanitise against this type of attack in version 5.2.16. All users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2024-07-17T19:36:00.563Z
Updated: 2024-08-02T02:27:53.196Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-48714 |
vulnerable | 2026-06-08 06:14:27.938620 |
Record titles for restricted records can be viewed if exposed by GridFieldAddExistingAutocompleter
MEDIUM (4.3)
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.
Published: 2024-01-23T13:49:27.350Z
Updated: 2025-06-17T21:19:26.348Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22729 |
vulnerable | 2026-06-08 05:54:26.978401 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22728 |
vulnerable | 2026-06-08 05:54:26.977159 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.