Synced 17 Jun 2026 22:27 UTC Account
← Silverstripe CMS

Silverstripe CMS vulnerabilities: known CVEs & security history

Silverstripe · CMS · 64 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Silverstripe CMS release lines — 64 in total. A CVE here doesn't mean your version is affected — check Silverstripe CMS's current status and the safe version to run.

64
known CVEs
0
actively exploited (KEV)
2
critical severity
0
ransomware-linked

Known Silverstripe CMS CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2019-12204 critical 9.8 1% 2019
CVE-2019-5715 critical 9.8 2% 2019
CVE-2007-2321 high 10 2% 2007
CVE-2019-12437 high 8.8 1% 2020
CVE-2020-6164 high 7.5 2% 2020
CVE-2020-9280 high 7.5 2% 2020
CVE-2011-4960 high 7.5 1% 2012
CVE-2008-6753 high 7.5 1% 2009
CVE-2009-1433 high 7.5 1% 2009
CVE-2011-4962 medium 6.8 4% 2012
CVE-2011-4959 medium 6.8 1% 2012
CVE-2010-4824 medium 6.8 3% 2012
CVE-2010-5088 medium 6.8 1% 2012
CVE-2010-5080 medium 6.8 1% 2012
CVE-2022-24444 medium 6.5 1% 2022
CVE-2021-41559 medium 6.5 1% 2022
CVE-2020-26136 medium 6.5 1% 2021
CVE-2019-12203 medium 6.3 0% 2019
CVE-2021-36150 medium 6.1 1% 2021
CVE-2019-19325 medium 6.1 1% 2020
CVE-2019-12205 medium 6.1 1% 2019
CVE-2017-14498 medium 6.1 1% 2017
CVE-2017-5197 medium 6.1 1% 2017
CVE-2015-8606 medium 6.1 2% 2016
CVE-2011-4961 medium 6 2% 2012
CVE-2010-5091 medium 6 1% 2012
CVE-2019-19326 medium 5.9 1% 2020
CVE-2015-5062 medium 5.8 2% 2015
CVE-2013-2653 medium 5.8 4% 2013
CVE-2017-18049 medium 5.5 1% 2018
CVE-2022-37421 medium 5.4 1% 2022
CVE-2022-28803 medium 5.4 0% 2022
CVE-2020-9311 medium 5.4 1% 2020
CVE-2019-14272 medium 5.4 1% 2019
CVE-2020-26138 medium 5.3 1% 2021
CVE-2020-6165 medium 5.3 1% 2020
CVE-2019-16409 medium 5.3 1% 2019
CVE-2019-14273 medium 5.3 1% 2019
CVE-2019-12245 medium 5.3 1% 2019
CVE-2017-12849 medium 5.3 1% 2017
CVE-2013-6789 medium 5 1% 2013
CVE-2010-5079 medium 5 2% 2012
CVE-2010-5078 medium 5 2% 2012
CVE-2010-5188 medium 5 2% 2012
CVE-2010-5094 medium 5 2% 2012
CVE-2010-5093 medium 5 2% 2012
CVE-2010-5087 medium 5 3% 2012
CVE-2020-25817 medium 4.8 1% 2021
CVE-2021-28661 medium 4.3 1% 2021
CVE-2019-12246 medium 4.3 1% 2020
CVE-2015-5063 medium 4.3 2% 2015
CVE-2011-4958 medium 4.3 4% 2014
CVE-2012-6458 medium 4.3 1% 2013
CVE-2012-4968 medium 4.3 2% 2012
CVE-2010-4823 medium 4.3 2% 2012
CVE-2010-4822 medium 4.3 2% 2012
CVE-2010-5187 medium 4.3 1% 2012
CVE-2010-5095 medium 4.3 2% 2012
CVE-2010-5089 medium 4.3 2% 2012
CVE-2010-1593 medium 4.3 3% 2010
CVE-2010-5090 medium 4 1% 2012
CVE-2019-12617 low 2.7 1% 2019
CVE-2012-0976 low 2.1 2% 2012
CVE-2010-5092 low 1.9 0% 2012

Is my Silverstripe CMS version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Silverstripe CMS version → · Monitor Silverstripe CMS for new CVEs →

Silverstripe CMS vulnerabilities — frequently asked

How many known vulnerabilities does Silverstripe CMS have?

IsItPatched tracks 64 CVEs for Silverstripe CMS. 2 are critical-severity and 7 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Silverstripe CMS have any actively-exploited vulnerabilities?

None of Silverstripe CMS's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Silverstripe CMS vulnerability?

Among tracked issues, CVE-2019-12204 (CRITICAL, CVSS 9.8) ranks highest.

Is Silverstripe CMS safe to use?

It depends on the version. The latest supported Silverstripe CMS release (6.2.0) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Silverstripe CMS security status · Silverstripe CMS end-of-life · actively-exploited CVEs. Always verify against Silverstripe's advisories — see our disclaimer.