A freelancer built your company’s website a couple of years ago. It works: customers fill in the quote form, the store takes payments, and nobody has touched it since it was handed over. Nobody at your company knows what PHP is, and there is no reason they should.
PHP is the language WordPress is written in; if your site is WordPress, it runs on PHP. If it runs on version 8.2, it stops getting security fixes on December 31.
What happens on December 31
The PHP project publishes its support schedule. Each version gets two years of full support, during which bugs and security issues are fixed, and two more years in which only critical security issues are fixed. After that it reaches end of life and nothing gets fixed.
PHP 8.2 came out on December 8, 2022, and its security support ends on December 31, 2026. Earlier versions have already ended: 8.1 on December 31, 2025, and 8.0 on November 26, 2023.
Your site does not go down on January 1. It keeps loading, the form keeps arriving and the store keeps charging. What ends is anyone fixing the flaws discovered from then on. PHP’s own page puts it this way: users of an unsupported version should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities.
It is not a rare case
WordPress publishes which PHP versions the sites it counts are running. Today, 22.4% run PHP 8.2 and another 31.9% run versions that are already out of support. Together that is 54.3%: more than half of those WordPress sites will start January on a PHP version with no patches.
WordPress recommends PHP 8.3 or newer. Its upgrade guide says versions older than 8.3 lack the latest security features.
How to check your version
- If your site is WordPress: in the dashboard, go to Tools, then Site Health, open the Info tab and expand the Server section. The PHP version is listed there.
- If you have no access to the dashboard or the hosting account, that is the first problem, and it is the same one as in Who actually owns your domain?: what belongs to your company cannot depend on the password of someone who is no longer around.
- If it is custom software written in PHP, such as a customer portal, ask whoever maintains it. If nobody does, start with You inherited software nobody documented.
Order matters
On many hosts, changing the PHP version means picking another one from a menu. Doing that first is the fastest way to take the site down. The order WordPress recommends:
- A backup, and one you can restore. If something breaks, you put the site back the way it was and ask your host to switch back to the previous PHP version. A backup you have never restored does not count; we explained why in A backup is worthless until you restore it.
- Update WordPress, the theme and the plugins before PHP. WordPress’s compatibility table says that 6.6 and earlier do not work with PHP 8.4, and 6.3 and earlier do not work with 8.3 either. Versions 7.0 and 7.1 work up to 8.5. If your site has gone years without updates, WordPress goes first.
- Check every plugin. WordPress tests its core on new versions, but says it does not know whether your theme and plugins will work. Check when each one was last updated. If one has gone a long time without an update or its developer cannot confirm it works, find another that does the same job.
- Test on a copy. If your host offers a staging site, change PHP there first.
- Switch the version and test what makes you money: the quote form, the cart, card payment and the confirmation email. The home page loading does not prove the cart can charge.
Which version?
Not the one that barely makes it. PHP 8.3 gets patches until December 31, 2027: jump to that one and in thirteen months you are back here. 8.4 gets them until December 31, 2028, and 8.5 until December 31, 2029. If your plugins allow it, go to 8.4 or 8.5.
If your host offers nothing newer than 8.2, that is an answer too: it is time to change hosts.
What to ask whoever runs your site
Before December 31, in writing:
- Which PHP version the site runs today and which one it will move to.
- The date of the change, and who tests the form and payments afterwards.
- The backup from before the change, and proof that it can be restored.
- Which plugins or parts of the site do not work on the new version, and what will be done about them.
It is the same story as Windows Server 2016 runs out of patches in January, but on the system your customers see.
Where we come in
We build and maintain websites, online stores and portals for companies of every kind in Juárez and El Paso: we check which PHP and WordPress versions yours runs and which plugins will not survive the change, then move it to a supported version, with a backup, and with the form and payments tested afterwards. If you want to know where to start, Chira asks the questions and tells you in writing. And if you would rather talk it through, book a call.
References
- Supported Versions, PHP — two years of full support and two of security fixes only; the dates for PHP 8.2 (released December 8, 2022, security support until December 31, 2026), 8.3 (until December 31, 2027), 8.4 (2028) and 8.5 (2029); and the advice to upgrade at end of life.
- Unsupported Branches, PHP — end of life for PHP 8.1 (December 31, 2025) and 8.0 (November 26, 2023).
- WordPress Statistics, WordPress.org — PHP versions on WordPress sites: 22.4% on 8.2 and 31.9% on 8.1 or older, checked on November 15, 2026.
- Requirements, WordPress.org — the recommendation of PHP 8.3 or newer.
- PHP Compatibility and WordPress Versions, WordPress.org — which WordPress versions work with each PHP version, and that core compatibility does not cover themes or plugins.
- Update PHP, WordPress.org — where to find the PHP version in Site Health, that versions older than 8.3 lack the latest security features, and the steps before switching: back up, update everything, check themes and plugins, test on a copy, and how to switch back.