HighGHSA-592m-4533-rxq9BIT-silverstripe-2020-9280CVE-2020-9280

SilverStripe Folders migrated from 3.x may be unsafe to upload to

Published 24 May 2022 · Updated 25 Apr 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=4.0.0 <4.4.6
Fixed in: 4.4.6

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.4.6

silverstripe/userformsComposer

Affected: >=5.0.0 <5.4.2
Fixed in: 5.4.2

Update to the fixed version for your release line, for example:composer require silverstripe/userforms:^5.4.2

silverstripe/assetsComposer

Affected: >=1.0.0 <1.4.7
Fixed in: 1.4.7

Update to the fixed version for your release line, for example:composer require silverstripe/assets:^1.4.7

silverstripe/assetsComposer

Affected: >=1.5.0 <1.5.2
Fixed in: 1.5.2

Update to the fixed version for your release line, for example:composer require silverstripe/assets:^1.5.2

Details

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.

Is GHSA-592m-4533-rxq9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.