Composer silverstripe/assets has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2020-9280 | SilverStripe Folders migrated from 3.x may be unsafe to upload to | high | 7.5 | >=1.0.0 and <1.4.7 or >=1.5.0 and <1.5.2 | 1.4.7, 1.5.2 |
| CVE-2019-12245 | Lack of access control on upoaded files | medium | 5.3 | >=1.0.0 and <1.3.5 or >=1.4.0 and <1.4.4 | 1.3.5, 1.4.4 |
| CVE-2022-29858 | Unpublished, protected files can be published via shortcode | medium | 4.3 | >=1.0.0 and <1.10.1 | 1.10.1 |
| CVE-2022-38724 | Silverstripe XSS in shortcodes | medium | 5.4 | >=1.0.0 and <1.11.1 | 1.11.1 |
| CVE-2022-38147 | XSS via uploaded gpx file | medium | 5.4 | >=1.0.0 and <1.11.1 | 1.11.1 |
| CVE-2026-24749 | Silverstripe Assets Module has a DBFile::getURL() permission bypass | medium | 5.3 | <2.4.5 or >=3.0.0 and <3.1.3 or >=2.0.0 and <2.4.5 | 2.4.5, 3.1.3 |
Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# one-time install pip install phpwarden # then phpwarden deps composer.lock
Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command
Install docs How findings are ranked