Complete end-of-life dates, support windows, and security status for all Silverstripe versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.3 | 2.3.13 | Feb 23, 2009 | Supported indefinitely | Supported | Active |
| 2.4 | 2.4.13 | Feb 2, 2011 | Mar 31, 2015 | 4057 days past EOL | EOL |
| 3.0 | 3.0.14 | Jun 28, 2012 | Oct 12, 2015 | 3862 days past EOL | EOL |
| 3.1 | 3.1.21 | Oct 1, 2013 | Dec 31, 2016 | 3416 days past EOL | EOL |
| 3.7 | 3.7.5 | Jun 8, 2018 | Sep 30, 2021 | 1682 days past EOL | EOL |
| 4.10 | 4.10.0 | Jan 27, 2022 | Dec 31, 2022 | 1225 days past EOL | EOL |
| 4.11 | 4.11.2 | Jun 28, 2022 | May 19, 2023 | 1086 days past EOL | EOL |
| 4.12 | 4.12.1 | Dec 19, 2022 | Oct 26, 2023 | 926 days past EOL | EOL |
| 4.13 | 4.13.0 | Apr 26, 2023 | Jun 10, 2025 | 333 days past EOL | EOL |
| 5.0 | 5.0.0 | May 8, 2023 | Apr 17, 2024 | 752 days past EOL | EOL |
| 5.1 | 5.1.0 | Oct 17, 2023 | Oct 17, 2024 | 569 days past EOL | EOL |
| 5.2 | 5.2.0 | Apr 15, 2024 | May 5, 2025 | 369 days past EOL | EOL |
| 5.3 | 5.3.0 | Nov 4, 2024 | Oct 11, 2025 | 210 days past EOL | EOL |
| 5.4 | 5.4.0 | Apr 10, 2025 | Apr 30, 2027 | 356 days remaining | Active |
| 6.0 | 6.0.0 | Jun 10, 2025 | Apr 14, 2026 | 25 days past EOL | EOL |
| 6.1 | 6.1.0 | Oct 13, 2025 | Oct 18, 2026 | 162 days remaining | Warning |
| 6.2 | 6.2.0 | Apr 17, 2026 | Apr 30, 2027 | 356 days remaining | Active |
When a Silverstripe version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Silverstripe should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →