SilverStripe Folders migrated from 3.x may be unsafe to upload to
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/framework Packagist |
|
|
| silverstripe/userforms Packagist |
|
|
| silverstripe/assets Packagist |
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/framework Packagist |
|
|
| silverstripe/userforms Packagist |
|
|
| silverstripe/assets Packagist |
|
|
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.
From the CVE record · mitre
After an upgrade from SilverStripe CMS 3.x to 4.x, files uploaded through Forms to migrated folders may be placed in the default /Uploads folder instead. This affects files uploaded after the upgrade on installations that used upload-folder protection through the optional silverstripe/secureassets module under 3.x. The input does not specify whether authentication is required.
Check installations using Packagist silverstripe/framework >=4.0.0 <4.4.6, silverstripe/userforms >=5.0.0 <5.4.2, or silverstripe/assets >=1.0.0 <1.4.7 or >=1.5.0 <1.5.2, particularly those upgraded from SilverStripe CMS 3.x with protected upload folders.