CVE-2020-9280: SilverStripe Folders migrated from 3.x may be unsafe to upload to

Quick answers

Is CVE-2020-9280 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-9280 being exploited in the wild.

How severe is CVE-2020-9280?

Low severity, with a CVSS score of 3.1, published 24 May 2022.

Which products and versions are affected?

silverstripe/assets (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.4.7; silverstripe/framework (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.6; silverstripe/userforms (Packagist) ECOSYSTEM:introduced=5.0.0,fixed=5.4.2.

Is there a fix for CVE-2020-9280?

Yes. silverstripe/assets (Packagist): upgrade to 1.4.7 or later; silverstripe/framework (Packagist): upgrade to 4.4.6 or later; silverstripe/userforms (Packagist): upgrade to 5.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2020-9280?

Check whether you run silverstripe/assets (Packagist), silverstripe/framework (Packagist) or silverstripe/userforms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• silverstripe/assets (Packagist): upgrade to 1.4.7 or later

  composer require silverstripe/assets:^1.4.7

• silverstripe/framework (Packagist): upgrade to 4.4.6 or later

  composer require silverstripe/framework:^4.4.6

• silverstripe/userforms (Packagist): upgrade to 5.4.2 or later

  composer require silverstripe/userforms:^5.4.2

Affected products

• silverstripe/assets (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.4.7
• silverstripe/framework (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.6
• silverstripe/userforms (Packagist) ECOSYSTEM:introduced=5.0.0,fixed=5.4.2

Identifiers

• CVE-2020-9280
• GHSA-592m-4533-rxq9