WordPress · Lifecycle Status

WordPress End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all WordPress versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

WordPress 7.0.1 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
7.0.1
7.0 series
Next EOL
None upcoming
Active Versions
1
of 35 total
EOL Versions
34
no longer patched
65 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Yes — CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20142015201620172018201920202021202220232024202520263.63.73.83.94.04.14.24.34.44.54.64.74.84.95.05.15.25.35.45.55.65.75.85.96.06.16.26.36.46.56.66.76.86.97.0TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
3.6 3.6.1 Aug 1, 2013 Oct 24, 2013 4645 days past EOL EOL
3.7 3.7.41 Oct 24, 2013 Dec 12, 2013 4596 days past EOL EOL
3.8 3.8.41 Dec 12, 2013 Apr 16, 2014 4471 days past EOL EOL
3.9 3.9.40 Apr 16, 2014 Sep 4, 2014 4330 days past EOL EOL
4.0 4.0.38 Sep 4, 2014 Dec 18, 2014 4225 days past EOL EOL
4.1 4.1.42 Dec 18, 2014 Apr 23, 2015 4099 days past EOL EOL
4.2 4.2.39 Apr 23, 2015 Aug 18, 2015 3982 days past EOL EOL
4.3 4.3.35 Aug 18, 2015 Dec 8, 2015 3870 days past EOL EOL
4.4 4.4.34 Dec 9, 2015 Apr 12, 2016 3744 days past EOL EOL
4.5 4.5.33 Apr 12, 2016 Aug 16, 2016 3618 days past EOL EOL
4.6 4.6.30 Aug 16, 2016 Dec 6, 2016 3506 days past EOL EOL
4.7 4.7.33 Dec 6, 2016 Jun 8, 2017 3322 days past EOL EOL
4.8 4.8.28 Jun 8, 2017 Nov 16, 2017 3161 days past EOL EOL
4.9 4.9.29 Nov 16, 2017 Dec 6, 2018 2776 days past EOL EOL
5.0 5.0.25 Dec 6, 2018 Feb 21, 2019 2699 days past EOL EOL
5.1 5.1.22 Feb 21, 2019 May 7, 2019 2624 days past EOL EOL
5.2 5.2.24 May 7, 2019 Nov 12, 2019 2435 days past EOL EOL
5.3 5.3.21 Nov 12, 2019 Mar 31, 2020 2295 days past EOL EOL
5.4 5.4.19 Mar 31, 2020 Aug 11, 2020 2162 days past EOL EOL
5.5 5.5.18 Aug 11, 2020 Dec 8, 2020 2043 days past EOL EOL
5.6 5.6.17 Dec 8, 2020 Mar 9, 2021 1952 days past EOL EOL
5.7 5.7.15 Mar 9, 2021 Jul 20, 2021 1819 days past EOL EOL
5.8 5.8.13 Jul 20, 2021 Jan 25, 2022 1630 days past EOL EOL
5.9 5.9.13 Jan 25, 2022 May 24, 2022 1511 days past EOL EOL
6.0 6.0.12 May 24, 2022 Nov 1, 2022 1350 days past EOL EOL
6.1 6.1.10 Nov 2, 2022 Mar 29, 2023 1202 days past EOL EOL
6.2 6.2.9 Mar 29, 2023 Aug 8, 2023 1070 days past EOL EOL
6.3 6.3.8 Aug 8, 2023 Nov 7, 2023 979 days past EOL EOL
6.4 6.4.8 Nov 7, 2023 Apr 2, 2024 832 days past EOL EOL
6.5 6.5.8 Apr 2, 2024 Jul 16, 2024 727 days past EOL EOL
6.6 6.6.5 Jul 16, 2024 Nov 12, 2024 608 days past EOL EOL
6.7 6.7.5 Nov 12, 2024 Apr 15, 2025 454 days past EOL EOL
6.8 6.8.5 Apr 15, 2025 Dec 2, 2025 223 days past EOL EOL
6.9 6.9.4 Dec 2, 2025 May 20, 2026 54 days past EOL EOL
7.0 7.0.1 May 20, 2026 TBD Supported Active

What does WordPress end of life mean for your organization?

When a version of WordPress 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 WordPress 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.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL WordPress versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get WordPress Support Options

WordPress has 34 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.

Get My Support Options →
Frequently Asked Questions
What is the end-of-life date for WordPress?
See the full table above for all WordPress version EOL dates.
When is the WordPress support end date?
Each WordPress version has its own support end date — see the table above for every version's date.
What is the latest supported version of WordPress?
The latest active version of WordPress is 7.0.1. Always verify against the table above as support windows can change.
What happens when WordPress reaches end of life?
When WordPress reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of WordPress?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL WordPress versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →