Approved changes feed: RSS · Atom
cpe:2.3:a:silverstripe:recipe:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Silverstripe (fb3ee4e6-70c4-5017-82a7-81441bb33bd1) |
|---|---|
| Product | Recipe (02d9bb0d-5818-5cd5-8efa-13ec4472bde7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/silverstripe/recipe-core |
purl2cpe | 2026-06-01 10:14:20.922244 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-9309 |
vulnerable | 2026-06-03 14:43:13.293963 |
Details available
Silverstripe CMS through 4.5 can be susceptible to script execution from malicious upload contents under allowed file extensions (for example HTML code in a TXT file). When these files are stored as protected or draft files, the MIME detection can cause browsers to execute the file contents. Uploads stored as protected or draft files are allowed by default for authorised users only, but can also be enabled through custom logic as well as modules such as silverstripe/userforms. Sites using the previously optional silverstripe/mimevalidator module can configure MIME whitelists rather than extension whitelists, and hence prevent this issue. Sites on the Common Web Platform (CWP) use this module by default, and are not affected.
Published: 2020-07-15T20:57:20.000Z
Updated: 2024-08-04T10:26:16.029Z |
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.