PHP 8.6 is scheduled for 19 November 2026. If you run a company with a WordPress site, an online shop or a custom-built platform, the new version changes nothing for you tomorrow.
The other end of the calendar is the one that concerns you. On 31 December 2026, PHP 8.2 stops receiving security fixes. And a great many sites run on versions that left the calendar years ago, without their owners knowing.
Below: what it means for a version to "expire", how to find out which one you have, and what exactly to ask your host.
Why a PHP version has an expiry date
PHP is the language your site is written in if you use WordPress, PrestaShop, Magento or custom code. It runs on the server, at your host, not inside the site. That is why you never see it and cannot update it from the dashboard where you write posts.
Every year, towards the end of November, a new version comes out. Each version gets four years of fixes: two years of fixes of every kind, then two more for security problems only. After those four years the PHP team publishes nothing further for it.
The site does not stop that day. It runs just as it did the day before. But when the next flaw is discovered, the versions in the calendar get the fix and yours does not. That is exactly what happened in October: anyone on PHP 8.1 or older was left without an official fix for two critical flaws.
The calendar, as of 18 November 2026
28 Nov 2022
PHP 7.4
Out of the calendarNo fixes for four years. Still one of the most widely used versions on WordPress sites.
26 Nov 2023
PHP 8.0
Out of the calendar31 Dec 2025
PHP 8.1
Out of the calendarReceived no official fix for the October 2026 flaws.
31 Dec 2026
PHP 8.2
In six weeksLast security fixes. If you are on 8.2, the move gets planned now.
31 Dec 2027
PHP 8.3
In the calendarSecurity fixes until this date.
31 Dec 2028
PHP 8.4
In the calendar31 Dec 2029
PHP 8.5
In the calendar
These are the dates the PHP team publishes on its supported-versions page. For 8.6, the page did not yet show its dates at the time of writing.
How many sites are already outside the calendar
- 44%
- of PHP sites run a version with no fixes: 5.x, 7.x, 8.0 or 8.1
- 17%
- are on PHP 8.2 and leave the calendar on 31 December 2026
- 14%
- of WordPress sites are still on PHP 7.4
The first two figures are our own calculation from W3Techs data of 18 November 2026. The third comes from WordPress.org statistics, read the same day.
In short: more than four PHP sites in ten already run without a net. From 1 January, almost two more join them.
Why not move to 8.6 on day one
The new version brings useful things for programmers and a few changes that can break an old site. Two examples, from the official upgrade notes:
- The default rules for sessions change, meaning the way a site remembers who is logged in. Older login code, or the return trip from a payment processor, may stop working without adjustments.
- Several functions that used to ignore a wrong value now raise an error. A carelessly written plugin that worked "by luck" can stop.
There is a simpler reason too. At the time of writing, the major platforms had not confirmed they run on 8.6:
- WordPress recommends "PHP 8.3 or greater", and its compatibility table has no column for 8.6 yet.
- WooCommerce says it is tested up to PHP 8.4.
- PrestaShop lists 8.6 as not supported.
- cPanel, a very widely used hosting control panel, offers versions up to 8.5.
You adopt a new version once your platform and your plugins say they run on it. That usually takes a few months.
Which version to ask for today
You are on PHP 7.4, 8.0 or 8.1
You are outside the calendar. Move to 8.3 or 8.4 now, not next year. The move is tested on a copy of the site first, because a lot changes between 7.4 and 8.x.
You are on PHP 8.2
You are covered until 31 December 2026. Plan the move to 8.3 or 8.4 in December, not in January, when everybody remembers at once.
You are on PHP 8.3, 8.4 or 8.5
You are fine. Just check that your host also applies the small updates to your version, the ones in the third number.
You are offered PHP 8.6
Ask first whether your platform and plugins support it. If the answer is "it should work", wait.
How to find out which version you have
In WordPress: Tools → Site Health → Info → Server. The line reads "PHP version". For other platforms, and for when you have no access to the dashboard, the steps are in the article on the October flaws.
What to write to your hosting provider
Message for your host, ready to send
Hello, Please confirm the exact PHP version running on my account (domain: …) and the date until which that version receives security fixes. If the version is 8.2 or older, please tell me which versions I can choose (8.3 or 8.4) and whether you can create a test copy of the site, so we can check the new version before the switch. Thank you.
A good answer contains a version number and a date. "Our servers are up to date" is not an answer.
Why the switch is not just a click
In the hosting panel you pick the PHP version from a list. It takes ten seconds. The problem is what happens next: an old theme, a plugin last updated in 2021 or a piece of code written for PHP 7 can stop the site with a blank page.
So the right order is: backup, test copy, switch the version on the test copy, check the pages that matter (contact form, basket, payment, login), and only then switch on the real site.
If someone looks after your site, send them this article. If nobody does, that is the real problem, and a bigger one than the PHP version.
Frequently asked questions
My site works fine. Why would I change the PHP version? Because "works" and "receives fixes" are different things. A version that has left the calendar runs exactly as before, until the first flaw for which no fix is published.
How much does changing the PHP version cost? At the host, usually nothing: you pick the version in the control panel. What costs is the checking beforehand and repairing whatever stops working afterwards. On a maintained site that is little work. On one untouched for years it can be a lot.
My host offers "extended support" for old PHP. Is that enough? Some hosting companies apply their own fixes to old versions. It is better than nothing and it buys you time. Ask exactly what it covers and until when, and use that time to move to a version that is in the calendar.
Do I need to update WordPress as well? Yes, they are two separate things. PHP belongs to the server, WordPress to the site. As of 18 November 2026, the current WordPress version is 7.1.4.
Sources: PHP, supported versions · PHP, end-of-life versions · PHP 8.6 upgrade notes · W3Techs, PHP usage · WordPress.org, requirements · WordPress, PHP compatibility · WooCommerce, server requirements · PrestaShop, system requirements · cPanel, MultiPHP Manager.
