The Silverstripe Assets Module is a required component of Silverstripe Framework. In versions prior to 2.4.5 and 3.0.0-rc1 through 3.1.2, images rendered in templates or otherwise accessed via DBFile::getURL() or DBFile::getSourceURL() incorrectly add an access grant to the curre...
Product
silverstripe/assets vulnerabilities
6 published CVES affecting silverstripe/assets, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 1
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest silverstripe/assets CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 0.41% PoC
-
CVE-2022-38147 XSS via uploaded gpx file
PublishedMediumCVSS 5.4 EPSS 0.66% PoCSilverstripe silverstripe/framework through 4.11 allows XSS (issue 3 of 3).
-
MediumCVSS 5.4 EPSS 0.82% PoC
Silverstripe silverstripe/framework through 4.11.0, silverstripe/assets through 1.11.0, and silverstripe/asset-admin through 1.11.0 allow XSS.
-
MediumCVSS 4.3 EPSS 1.3% PoC
Silverstripe silverstripe/assets through 1.10 is vulnerable to improper access control that allows protected images to be published by changing an existing image short code on website content.
-
HighCVSS 7.5 EPSS 1.7% PoC
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....
-
MediumCVSS 5.3 EPSS 1.4% PoC
SilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.