Is silverstripe/cms vulnerable?

Composer silverstripe/cms has 19 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

19advisories
1critical
0on CISA KEV
4no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2011-4962Silverstripe CMS Arbitrary Code Executionmedium0.0>=2.4.0 and <2.4.62.4.6
CVE-2010-1593SilverStripe vulnerable to Cross-site Scriptinglow0.0<2.3.52.3.5
CVE-2015-5062Silverstripe CMS Open Redirectmedium0.0<=3.1.13–
CVE-2020-9309Silverstripe CMS malicious file upload enables script executionhigh8.8<=4.5.0–
CVE-2020-6164Silverstripe CMS information disclosurehigh7.5<=4.5.0–
CVE-2015-8606Silverstripe CMS XSS Vulnerabilitymedium6.1<3.1.16 or >=3.2.0 and <3.2.13.1.16, 3.2.1
CVE-2019-12204Missing warning can lead to unauthenticated admin access in SilverStripecritical9.8>=4.4.0 and <4.4.44.4.4
CVE-2017-14498Silverstripe CMS XSS Vulnerabilitymedium6.1<3.6.13.6.1
CVE-2017-12849Silverstripe CMS User Enumerationmedium5.3<3.5.5 or >=3.6 and <3.6.13.5.5, 3.6.1
CVE-2017-5197Silverstripe CMS XSS Vulnerabilitymedium6.1<3.4.4 or >=3.5.0 and <3.5.23.4.4, 3.5.2
CVE-2022-37421Silverstipe CMS Stored XSS in custom meta tagsmedium5.4>=4.0.0 and <4.11.34.11.3
CVE-2020-9311Silverstripe CMS XSS Vulnerabilitymedium5.4<=4.5.0–
CVE-2026-54717Silverstripe: XSS in breadcrumbs in page list viewmedium5.4<6.2.16.2.1
GHSA-3mm9-2p44-rw39Silverstripe SiteTree Creation Permission Vulnerabilityhigh7.5>=3.0.0 and <3.0.12 or >=3.1.0 and <3.1.113.0.12, 3.1.11
GHSA-6hh6-59j2-qrxwSilverstripe History XSS Vulnerabilitymedium6.1>=3.1.0 and <3.1.103.1.10
GHSA-r97r-64vp-fghmSilverstripe XSS vulnerability via VirtualPagemedium6.1>=3.1.0 and <3.1.103.1.10
SS-2015-003-1SS-2015-003: History XSS Vulnerabilityunknown0.0>=3.1.0 and <3.1.103.1.10
SS-2015-005-1SS-2015-005: VirtualPage XSSunknown0.0>=3.1.0 and <3.1.103.1.10
SS-2015-008-1SS-2015-008: SiteTree Creation Permission Vulnerabilityunknown0.0>=3.0.0 and <3.0.12 or >=3.1.0 and <3.1.113.0.12, 3.1.11

Am I affected?

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
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.