PHP and WordPress Version Upgrades | The Risk of Old Versions and How to Update Safely
On this page
- Working is not the same as safe
- PHP support periods are fixed in advance
- A recent example of a serious vulnerability
- WordPress and PHP belong together
- Waiting makes the work larger
- What people worry about
- How we work
- When migration or a rebuild fits better
- In-house or commissioned
- About cost
- Start by checking your current version
"It is working, so it is safer not to touch it." If you look after a website or business system built on PHP or WordPress, you may well have thought this. The worry is reasonable: an update can break a layout or stop a form from working, and upgrade work does call for care.
But PHP and WordPress do not stand still while you leave them alone. Support periods end and fixes stop arriving. A serious vulnerability is found and a patched version has to be installed quickly. Plugins you rely on stop working with the version you are running. All of this can happen without a single change to your site.
This page explains why upgrading PHP and WordPress matters, what can happen if it is put off, and how an upgrade can be carried out safely. We take on version upgrades for PHP-based systems and WordPress sites that are already running. We hope it helps you decide what to do.
Working is not the same as safe
A site that displays correctly and sends its contact form looks healthy. But what you see on screen says nothing about security. An old PHP or WordPress version looks exactly the same in daily use. A vulnerability becomes a problem when someone tries to exploit it, so a site can appear to be fine right up to the day it is not. By the time an alteration or a leak of stored information is noticed, it may already have been going on for some time.
It is also easy to overlook that PHP and WordPress are not supported forever. Each version has a defined support period. After it ends, fixes are no longer released for newly found problems.
PHP support periods are fixed in advance
Each PHP branch has an active support period and a security support period. Once active support ends, only security fixes continue, and after security support ends nothing is released. The PHP project urges users of an unsupported release to upgrade as soon as possible, since they may be exposed to unpatched vulnerabilities.
As of November 16, 2026, the PHP support periods are as follows.
| PHP version | Active support ends | Security support ends |
|---|---|---|
| 8.2 | December 31, 2024 | December 31, 2026 |
| 8.3 | December 31, 2025 | December 31, 2027 |
| 8.4 | December 31, 2026 | December 31, 2028 |
| 8.5 | December 31, 2027 | December 31, 2029 |
PHP 8.1 and earlier, which are not in this table, are already out of support. Even PHP 8.2 has only about six weeks of security support left at the date above. Dates can be revised by the PHP project, so it is worth checking the current table when you plan an upgrade.
A recent example of a serious vulnerability
In October 2026, two serious PHP vulnerabilities were reported and patched versions were released. They are of the kind that could let a third party who is not logged in run programs on a web server from the outside. Because the problem lies in PHP itself, it cannot be solved by careful work on the site's own code. PHP has to be updated.
For how the issue works, how large its impact is, how to check your version and what to do if you cannot update immediately, see an explainer on the critical PHP vulnerabilities (307.jp, in Japanese). It is written for readers new to the subject.
The lesson is that vulnerability response is not something a site owner can schedule. A patched version appears on a certain day and you need to move quickly. Whether you are on a version that can be updated, and whether the update procedure is ready, decides how fast you can respond. If an old version has been left alone, there may be no patched release at all, and you may have to jump straight to a much newer one.
WordPress and PHP belong together
For a WordPress site, it helps to think of PHP and WordPress itself as a pair. WordPress runs on PHP, so updating only one can cause problems depending on the combination.
WordPress recommends PHP 8.3 or greater. It also works with PHP 7.4 and later, but those older versions have reached end of life and may expose a site to security vulnerabilities. A WordPress core that is up to date therefore does not make a site safe if the PHP beneath it is old.
The same applies to WordPress core. Only the latest version is supported. Fixes are sometimes backported to older versions, but that is a courtesy, not a standing commitment.
Themes and plugins
A WordPress site also runs a theme for design and plugins for added features. These are developed by separate parties, and each supports different versions of PHP and WordPress. After updating PHP or WordPress, an older plugin may stop working. In the other direction, a plugin updated first may no longer run on an old PHP. Checking these combinations is why upgrade work needs care.
Waiting makes the work larger
Putting off updates also tends to make them heavier. The larger the gap between versions, the more has changed. With small, regular updates, each step has few changes, and when something breaks the cause is easy to find. A site left for years and brought up to date in one step has to absorb everything at once, including features removed in newer versions and plugins that no longer work.
An update forced by a deadline, such as the end of support or a newly announced vulnerability, also leaves little room for testing, and things get missed. Planning ahead is, we believe, both safer and easier on cost.
What people worry about
The common worries are a broken layout, features that stop working, such as form submission or members' pages, and an update that leaves the site unable to load. These can be reduced a great deal by how the work is done: try the update first in a test environment that mirrors the live site, take a backup beforehand, and decide in advance how to return to the previous state.
How we work
We proceed in this order.
Checking the current state
We confirm the PHP and WordPress versions in use, the theme and plugins, and the server environment. Some sites run on rental servers where the PHP version is switched in a control panel; others run on dedicated servers or containers. The procedure and the points to watch differ.
Assessing the impact
We work out how far the versions can be raised and what is likely to stop working. We check plugin compatibility and whether custom code contains constructs no longer usable in newer versions. This gives us a view of the amount of work.
Verifying in a test environment
We prepare a test environment with the same content as the live site and carry out the update there. We check the key behavior one item at a time: page display, contact form submission, members' features and so on. Any problem can be investigated and fixed without affecting the live site.
Updating the live site and restarting
Once the test environment shows no problems, we update the live site. A PHP update does not take effect until the running processes are restarted, so we include the restart in the work. This prevents the case where an update was applied but the old version is still running.
Checking afterward
After the update we confirm the PHP version actually running, the error records and form submission. We keep the pre-update state so that we can return to it quickly if something is wrong.
When migration or a rebuild fits better
An upgrade is not always a simple "update and done." For a system on PHP 8.1 or earlier, which is already out of support, many old constructs may need rewriting to reach a current version. In that case it is worth comparing the amount of work with the cost of rebuilding. If the site's design or usability is also a concern, doing the update together with a renewal can waste less effort. Our approach to renewals is described in how to renew a website.
If the features and appearance are fine and only the version is old, upgrading alone is the better fit. We will consider with you, after seeing the state of the site, which is appropriate. We do not recommend a rebuild when an upgrade will do.
In-house or commissioned
If you have a capable person in-house and can prepare a test environment, doing it yourselves is a reasonable option. Even then, we suggest keeping the backup beforehand and a way to return to the previous state. If the person in charge is handling other duties or no one is familiar with server settings, the work tends to slip past its deadline.
When you commission us, we handle everything from the initial check through testing, the live update and the final verification. A split is also possible: we do the upgrade and you continue routine content updates yourselves.
About cost
The cost varies with the size of the site or system, the gap between the current and target versions, and the number of plugins and custom features. A small site of a few pages and a business system with many custom features need very different work, so we do not publish a fixed price. We hear about your situation and return the scope of work and a rough estimate. When comparing quotations, it is worth checking what is included, such as testing and post-update verification.
Start by checking your current version
The first step is to find out which PHP version you are running. On a rental server, the server company's control panel often shows it. On WordPress, the Site Health screen in the admin area also shows it. If the version is out of support or close to the end of support, we suggest planning an upgrade soon.
If you are not sure how to check, or how to judge what you find, please tell us your situation: the versions in use if you know them, the type of site, and what worries you about updating. We will tell you whether an upgrade is needed and in what order it could proceed.
For the whole picture of our system development, see system development for subsidy program secretariats. Our approach to websites is on the page about website production in Hyogo and Okayama.