CVE-2020-9280 json
SilverStripe Folders migrated from 3.x may be unsafe to upload to
published 6y ago modified 4mo ago also BIT-silverstripe-2020-9280 , EUVD-2022-2539 , GHSA-592m-4533-rxq9
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 4.4.6
- packagist silverstripe/userforms 5.4.2
- packagist silverstripe/assets 1.4.7, 1.5.2
- bitnami silverstripe 4.5.0
Is CVE-2020-9280 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.0.0, <4.4.6 |
4.4.6 |
| packagist | silverstripe/userforms | >=5.0.0, <5.4.2 |
5.4.2 |
| packagist | silverstripe/assets | >=1.0.0, <1.4.7 >=1.5.0, <1.5.2 |
1.4.7 1.5.2 |
| bitnami | silverstripe | >=4.0.0, <4.5.0 |
4.5.0 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/silverstripe/silverstripe-assets/commit/6779fd3c8c1c05a3db5035bf6e541c9483d161fc
web
-
github.com
/silverstripe/silverstripe-userforms/commit/3bbad2044279ade5e5a5d0ae1822bafe479f8a26
web
-
silverstripe.org
/download/security-releases/
vendor-advisory, web
-
forum.silverstripe.org
/c/releases
web, vendor-advisory
-
silverstripe.org
/download/security-releases/cve-2020-9280
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-9280
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/assets/CVE-2020-9280.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
silverstripe.org
/download/security-releases
web
Sources
- CVE List CVE-2020-9280
- GitHub Advisory GHSA-592m-4533-rxq9
- NVD CVE-2020-9280
- OSV BIT-silverstripe-2020-9280
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.