First published: Wed Jul 15 2020(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/silverstripe/cms | <=4.5.0 | |
Silverstripe Mimevalidator | <2.0.0 | |
Silverstripe Recipe | >=4.0.0<4.6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-9309 is a vulnerability in Silverstripe CMS through version 4.5 that allows script execution from malicious upload contents.
CVE-2020-9309 has a severity score of 8.8, which is considered high.
Silverstripe CMS through version 4.5 can be vulnerable to CVE-2020-9309 if malicious upload contents are allowed under file extensions and stored as protected or draft files.
CVE-2020-9309 can allow an attacker to execute scripts through the file contents of malicious uploads in Silverstripe CMS.
To mitigate CVE-2020-9309, ensure that only trusted file extensions are allowed for upload contents and consider validating file contents against their declared MIME types.