Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Statistics · Info

How Long Is a WordPress Version Supported?

Short answer

Only the latest major WordPress version is actively supported, and WordPress publishes no fixed support period for it. When a new major version ships, the previous version stops getting bug fixes and new features. Security fixes may still be backported to older branches back to 4.7, but only as a courtesy, with no guarantee and no schedule.

Key takeaways

  • Only the latest major WordPress version is actively supported, with no fixed end date published.
  • WordPress has no long-term support version, so no branch gets a promised number of years.
  • Security fixes are backported as a courtesy to branches back to 4.7, with no guarantee.
  • Versions 4.6 and earlier no longer receive security updates at all.
  • WordPress 7.0 was the latest version for about 3 months, from 20 May 2026 to 19 August 2026.
  • PHP 8.2 security support ends on 31 December 2026, which can force an upgrade even on a patched WordPress branch.

How long is a WordPress version supported?

Only the latest major WordPress version is actively supported, and WordPress publishes no fixed end date for it.

WordPress.org states this plainly on its Supported Versions page. The page says the only current officially supported version is the last major release. Previous major releases may or may not get security updates when serious exploits are found.

That answer surprises many site owners. Most software gives each version a set number of years, but WordPress does not work that way. The length of active support depends on when the next major version ships, so it changes with each release cycle.

The policy reaches a large share of the web. The HTTP Archive Web Almanac 2024 found WordPress on over 35% of mobile sites in its dataset, and 51% of desktop sites in the dataset used a CMS.

What does “actively supported” mean in WordPress?

Active support means a version gets bug fixes, new features, and security fixes, while older branches get security fixes only when the security team backports them.

WordPress.org also states that there is no fixed period of support and no long-term support version, using Ubuntu as the contrast in its Supported Versions page.

A long-term support version is a release that a project promises to maintain for a set number of years. WordPress has no such release, so you cannot plan around a promised end date for any branch.

Beta versions, nightly builds, and Subversion checkouts get no support on the WordPress.org forums or in WordPress documentation, according to the same page. If you run one of those, you are on your own.

For more on the idea of a long-term version, see what WordPress LTS means.

How long was WordPress 7.0 supported?

WordPress 7.0 was the latest version for about 3 months, from 20 May 2026 until WordPress 7.1 arrived on 19 August 2026.

That short window shows how the policy works in practice. Active support for 7.0 ended the day 7.1 shipped, not on a date announced years in advance. The branch then moved to security backports only, and its latest patch became 7.0.9 on 18 November 2026.

The previous branch lasted longer. WordPress 6.9 shipped on 2 December 2025 and stayed the latest version until 7.0 arrived on 20 May 2026, a span of about 5 months. Its latest patch is now 6.9.12, also dated 18 November 2026.

In 2026, WordPress shipped 7.0 in May and 7.1 in August, and the WordPress 7.1.5 release post says the next major release, 7.2, is planned for 8 December 2026. Each new major release resets the clock. For the wider pattern, see how the WordPress release cycle works.

Do older WordPress versions still get security updates?

Yes, older branches back to 4.7 still receive security fixes as a courtesy, but WordPress gives no guarantee and no schedule for them.

The WordPress 7.1.5 release post says the fixes were backported to all branches eligible to receive security fixes, currently through 4.7. It repeats the reminder that only the most recent version is actively supported.

The scale of those backports is large. WordPress 7.1.4, released on 28 October 2026, fixed 22 vulnerabilities, according to its version 7.1.4 page. WordPress 7.0 and 6.9 were affected by all 22, and WordPress 4.7 was affected by 2 of the 22.

WordPress 7.1.5, released on 18 November 2026, fixed 20 vulnerabilities, according to its version 7.1.5 page. WordPress 7.0 and 6.9 were affected by all 20, while WordPress 4.7 was affected by 11 of the 20. The patched releases that day were 7.0.9, 6.9.12, 6.8.13, and 4.7.40.

BranchLatest patch as of November 2026What it still gets
7.17.1.5, 18 November 2026Full active support
7.07.0.9, 18 November 2026Security backports only
6.96.9.12, 18 November 2026Security backports only
6.86.8.13, 18 November 2026Security backports only
4.74.7.40, 18 November 2026Security backports only
4.6 and earlier4.6.30, July 2025No security updates

A backport is not the same as support. Bug fixes and new features do not travel back to old branches, and a fix that cannot be backported cleanly may never reach them.

Staying patched matters in real cleanups. Sucuri's 2023 Hacked Website and Malware Threat Report found 39.1% of CMS applications outdated at the point of infection. For the security side of staying current, see whether WordPress is secure.

When did WordPress stop security updates for very old versions?

WordPress stopped security updates for versions 4.1 through 4.6 in July 2025, after backports had reached back to 4.1 since December 2022.

WordPress.org announced the July 2025 cutoff in its post on dropping security updates for WordPress versions 4.1 through 4.6. The post says those versions were first released 9 or more years ago, and that over 99% of WordPress installations run a more recent version.

The cutoff is a reminder that courtesy backports can end with short notice. The June 2025 announcement came about a month before the July 2025 cutoff. There is no published timetable for when the next cutoff will happen, or which branches it will cover.

WordPress.org also notes in the same post that the only actively supported version is the most recent one, and that security updates are backported to older branches only as a courtesy. A site on 4.6 or earlier gets nothing now, even if a new flaw affects it.

How does PHP support affect how long a WordPress version lasts?

PHP support can end a WordPress version sooner in practice, because each PHP branch gets security fixes for only 4 years.

The PHP project gives each branch 2 years of active support and then 2 years of security fixes only, according to the PHP supported versions page. After the security period ends, the branch gets no further fixes from the PHP project.

PHP branchActive support untilSecurity fixes until
8.231 December 202431 December 2026
8.331 December 202531 December 2027
8.431 December 202631 December 2028
8.531 December 202731 December 2029

That matters because an old WordPress branch can cap the PHP version you can use. WordPress 7.0 raised the minimum PHP version to 7.4.0, according to the Make WordPress Core post on dropping support for PHP 7.2 and 7.3.

Sites still on PHP 7.2 or 7.3 stay on the 6.9 branch when 7.0 ships.

WordPress.org recommends PHP 8.3 or newer for running WordPress, as of November 2026. PHP 8.2 security support ends on 31 December 2026, so a site on PHP 8.2 needs a PHP move by then even if its WordPress branch still gets backports.

See which PHP version to use for WordPress before you pick a target.

How do you check which version your site runs and whether it is supported?

Check Dashboard, then Updates in your admin area, and compare the number there with the latest release on WordPress.org.

WordPress.org says the version you run appears at the bottom of the At a Glance section of the dashboard. An out-of-date version shows a notice in the dashboard, such as a message that a newer version is available and that you should update now.

The WordPress 7.1.5 release post gives the update path: visit the Dashboard, click Updates, and then click Update Now. Sites that support automatic background updates begin the update on their own.

As of November 2026, the latest release is WordPress 7.1.5, released on 18 November 2026. If your dashboard shows any other number, you are not on the actively supported version. If it shows 4.6 or earlier, you are on a branch that gets no security updates at all.

What should you do when your version stops being the latest?

Move to the latest major version soon after it ships, after a backup and a check of your plugins and theme.

A short, planned move beats a forced one later. Follow these steps in order:

  1. Back up your site and database first, so you can restore it if the update fails. See how to back up WordPress.
  2. Check your PHP version against the new WordPress version, and ask your host to move PHP first if it is too old. See how to update the PHP version in WordPress.
  3. Update your plugins and theme, then update WordPress itself from Dashboard, then Updates.
  4. Check the front page, login page, and main forms after the update, and restore the backup if anything breaks.

If you cannot move to the latest major version yet, at least take the latest patch on your own branch.

That patch carries the backported security fixes, and it arrives through the normal minor update channel. Staying on an unpatched point release, such as 7.1.3 after 7.1.5 ships, leaves known flaws open.

What mistakes should you avoid?

Avoid treating backports as a promise, waiting for a published end date, and ignoring PHP dates.

  • Treating a backport as a promise. Security fixes for old branches are a courtesy, and WordPress gives no guarantee that the next fix will be backported.
  • Waiting for a published end date. WordPress publishes no end date for any version, so a branch can lose backports with about a month of notice, as 4.1 through 4.6 did in 2025.
  • Ignoring PHP dates. A patched WordPress branch on PHP 8.2 still loses PHP security fixes on 31 December 2026.
  • Turning off minor updates. Minor updates carry the backported security fixes, so switching them off cuts off the only fixes an old branch still gets.
  • Staying on 4.6 or earlier. Those branches get no security updates at all, and no setting can bring them back.

Frequently asked questions

Does WordPress have a long-term support version?

No. WordPress.org states that there is no fixed period of support and no long-term support version. Only the latest major version is actively supported, and older branches get security fixes only as a courtesy. If you need a promised number of years, WordPress does not offer one.

How long did WordPress 6.9 stay supported?

WordPress 6.9 was the latest version from 2 December 2025 until WordPress 7.0 shipped on 20 May 2026, about 5 months. After that it moved to security backports only. Its latest patch is 6.9.12, released on 18 November 2026, which shows backports can continue for many months after active support ends.

Is WordPress 4.7 still safe to use?

No, not as a long-term choice. WordPress 4.7 still received a backported patch, 4.7.40, on 18 November 2026, but it gets no bug fixes or new features, and future security fixes are not guaranteed. It also cannot run newer PHP versions, so move to the latest WordPress version as soon as you can.

What happens when WordPress 7.2 is released?

WordPress 7.1 will stop being actively supported on the day 7.2 ships, which is planned for 8 December 2026. WordPress 7.1 will then move to security backports only, like 7.0 and 6.9 today. Plan your move to 7.2 soon after it ships, after a backup and a PHP check.

Do plugins and themes follow the same support rule?

No. Each plugin and theme sets its own minimum WordPress version and its own update schedule, and authors can drop old WordPress versions at any time. An old WordPress branch may still get core security backports while its plugins stop supporting it, which is another reason to move to the latest version.

Sources

  1. Supported Versions WordPress.org
  2. WordPress 7.1.5 Release WordPress.org
  3. Dropping security updates for WordPress versions 4.1 through 4.6 WordPress.org
  4. Version 7.1.5 WordPress.org
  5. Version 7.1.4 WordPress.org
  6. Supported Versions PHP Group
  7. CMS | 2024 | The Web Almanac by HTTP Archive HTTP Archive
  8. 2023 Hacked Website and Malware Threat Report Sucuri

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test