← ← Back to all products
All badges & lifecycle API →
Silverstripe CMSEnd of Life (EOL) Dates & Support Status
Active
CMS & ContentLatest Version: 6.2.0Latest Release: Apr 17, 2026
Silverstripe is a flexible PHP CMS and framework for building and maintaining websites.
Support summary
Silverstripe CMS 6.1 reaches EOL in 21 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Oct 18, 2026
Silverstripe CMS 6.1 · 21 days left
Supported cycles
3
0 lts
Versions
17
Latest Version
6.2.0
Active Support
1
EOL
14
Lifecycle Timeline
Dec 19, 2022As of Sep 27, 2026
6.2Active · Apr 30, 2027
6.1Security · Oct 18, 2026
6.0EOL · Apr 14, 2026
5.4Security · Apr 30, 2027
5.3EOL · Oct 11, 2025
5.2EOL · May 5, 2025
5.1EOL · Oct 17, 2024
5.0EOL · Apr 17, 2024
4.13EOL · Jun 10, 2025
4.12EOL · Oct 26, 2023
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 6.2 | Apr 17, 2026 | Oct 31, 2026 | Apr 30, 2027 | 6.2.0 | No | Active |
| 6.1 | Oct 13, 2025 | Apr 17, 2026 | Oct 18, 2026 | 6.1.0 | No | Security |
| 6.0 | Jun 10, 2025 | Oct 13, 2025 | Apr 14, 2026 | 6.0.0 | No | EOL |
| 5.4 | Apr 10, 2025 | Apr 11, 2026 | Apr 30, 2027 | 5.4.0 | No | Security |
| 5.3 | Nov 4, 2024 | Apr 10, 2025 | Oct 11, 2025 | 5.3.0 | No | EOL |
| 5.2 | Apr 15, 2024 | Nov 4, 2024 | May 5, 2025 | 5.2.0 | No | EOL |
| 5.1 | Oct 17, 2023 | Apr 17, 2024 | Oct 17, 2024 | 5.1.0 | No | EOL |
| 5.0 | May 8, 2023 | Oct 17, 2023 | Apr 17, 2024 | 5.0.0 | No | EOL |
| 4.13 | Apr 26, 2023 | Apr 27, 2024 | Jun 10, 2025 | 4.13.0 | No | EOL |
| 4.12 | Dec 19, 2022 | Apr 26, 2023 | Oct 26, 2023 | 4.12.1 | No | EOL |
| 4.11 | Jun 28, 2022 | Dec 19, 2022 | May 19, 2023 | 4.11.2 | No | EOL |
| 4.10 | Jan 27, 2022 | Jun 30, 2022 | Dec 31, 2022 | 4.10.0 | No | EOL |
| 3.7 | Jun 8, 2018 | Ended | Sep 30, 2021 | 3.7.5 | No | EOL |
| 3.1 | Oct 1, 2013 | Ended | Dec 31, 2016 | 3.1.21 | No | EOL |
| 3.0 | Jun 28, 2012 | Ended | Oct 12, 2015 | 3.0.14 | No | EOL |
| 2.4 | Feb 2, 2011 | Ended | Mar 31, 2015 | 2.4.13 | No | EOL |
| 2.3 | Feb 23, 2009 | Ended | Ended; date not announced | 2.3.13 | No | EOL |
Data sources
Embed this badge
Show Silverstripe CMS's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/silverstripe/)HTML
<a href="https://eol.wiki/silverstripe/"><img src="https://eol.wiki/badge/silverstripe.svg" alt="Silverstripe CMS end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Silverstripe CMS have reached end of life?
The following Silverstripe CMS versions have reached end of life and no longer receive security updates: 6.0, 5.3, 5.2, 5.1, 5.0, 4.13, 4.12, 4.11 (and 6 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Silverstripe CMS 6.0?
Silverstripe CMS 6.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Silverstripe CMS?
The latest version of Silverstripe CMS is 6.2.0, released in the 6.2 release cycle.
How many versions of Silverstripe CMS are currently supported?
Silverstripe CMS currently has 3 actively supported version(s): 6.2, 6.1, 5.4.
When does Silverstripe CMS 6.2 reach end of life?
Silverstripe CMS 6.2 is scheduled to reach end of life on Apr 30, 2027.
What should I do when Silverstripe CMS reaches end of life?
When a Silverstripe CMS version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.