Skip to content
A paper shield with an orange check mark next to server racks — website protection after a PHP update
Services / PHP update
Critical PHP vulnerabilities · 10/21/2026

Urgent PHP update for your website

On October 21, PHP closed two critical vulnerabilities rated CVSS 9.2. They are known as php2shell (CVE-2026-109618 and CVE-2026-109619): they let an attacker run code on your server without a login. The exploit is already public, and Cloudflare is recording the first attack attempts. We'll check your site for free and update PHP so that nothing breaks.

  • 15 minPHP version check
  • from $25update per hour
  • 1 hrreply during business hours

You need to update PHP now, but without the site going down

A PHP update means moving your site to a version of the language that the PHP developers support and for which security fixes are released. After 10/21/2026 only 8.5.12, 8.4.27, 8.3.36 and 8.2.35 and newer builds of those branches are considered safe.

Most often the host updates the minor version by itself. But if a site is still on 8.1, 7.4 or older, there are no official patches for it at all: you have to move to a newer branch. This is exactly where old plugins and themes crash with an error and the site shows a white screen.

We work with sites on WordPress, WooCommerce, OpenCart and custom code, including ones we didn't build.

01

Is your site at risk

Below is only what PHP officially wrote in its October 21 security bulletin. No guesswork and no scare stories.

SituationWhat it meansWhat to do
PHP 8.5, 8.4, 8.3 or 8.2Vulnerable up to builds 8.5.12, 8.4.27, 8.3.36 and 8.2.35Update to the fixed build and check that your host has already installed it
PHP 8.1, 8.0, 7.xNo updates from the PHP project. Some Linux vendors and hosts make their own patchesMove to 8.3 or 8.4 with a compatibility check
PHP 8.2Fixed, but support ends on 12/31/2026Update now and plan a move to 8.3/8.4 before the end of the year
Apache with mod_phpHighest risk: the attack works before your site's code even runsUpdate as a priority
PHP-FPM, php-cgi, LiteSpeed, FrankenPHPAlso affected: any PHP that handles web requestsUpdate and restart all PHP workers

The temporary settings from the bulletin (disable session.upload_progress, limit post_max_size) only reduce the risk and do not replace an update. On ordinary hosting some of them are not even available. For a detailed breakdown, read the article php2shell: what a site owner should do.

02

How to find your PHP version in 3 minutes

01
WordPress: "Site Health"

Admin panel → Tools → Site Health → Info → the "Server" section. It shows the exact version, for example 8.3.36.

02
Hosting panel

In hPanel, cPanel or ISPmanager the PHP version is shown in the site settings. It is also changed there, but you shouldn't do that blindly on a live site.

03
The phpinfo file

A file with a single line <?php phpinfo(); will show the version and all settings. Delete it right after checking: it exposes your server configuration to anyone.

Don't want to dig into the admin panel? Send us your site address and we'll tell you the version and the risks within 15 minutes during business hours. For free.

03

What breaks during a PHP update

Changing the version itself takes a minute. The hours go into making sure the site works after it exactly as it did before.

Old plugins

Plugins that haven't been updated for years use functions removed in PHP 8. A single such plugin takes down the whole site.

Themes and page builders

Themes bought long ago and old versions of page builders break the layout or throw errors on individual pages.

Bitrix, OpenCart, custom code

Old core versions and modifications often won't start on PHP 8.x without code changes. This calls for an assessment, not a button in a panel.

"Critical error"

A white screen or the message "There has been a critical error on this website". How to find the culprit is explained in a separate article.

04

How much a PHP update costs

Update
A site on 8.2–8.5 where the fixed build needs installing and the site needs testing.
from$25
one-time · 1 hour of work
  • Version and settings check
  • Backup before any changes
  • Update to the fixed build
  • Check of the home page, forms and cart
Order
Turnkey
Move to 8.3/8.4
A WordPress brochure or corporate site on PHP 8.1 and older.
$50
fixed price · stores quoted after a check
  • Full backup of files and database
  • A copy of the site on a test staging environment
  • PHP 8.3 or 8.4 on the staging site
  • Check of the theme and every plugin
  • Switching the live site over
  • 48-hour error monitoring
Order
The site is already down
A white screen, a "critical error" or a hack after your host updated PHP.
$25
per hour · we start the same day you contact us
  • Finding the cause in the error logs
  • Getting the site temporarily back online
  • Replacing or fixing the incompatible code
  • A check for signs of a hack
Urgent

Checking your PHP version and risks is free, and we reply within an hour during business hours. For a store or a site on custom code we name the exact amount before work begins. So you don't have to come back to this in six months, you can put your site on support, where updates and backups happen every month.

05

How we update PHP

01
Backup

A full copy of the files and the database before any changes. We don't start without it.

02
Staging

We deploy a copy of the site separately from the live one, so that we see the errors, not your customers.

03
New version

We install PHP 8.3 or 8.4, go through the error log and fix whatever is incompatible.

04
Switch-over

We change the version on the live site during a quiet hour and check forms, payment and email.

05
48 hours

We watch the error log for two days and fix whatever surfaces under real traffic.

06

Frequently asked questions

What is php2shell?

This is what the security community called two critical PHP vulnerabilities closed on October 21, 2026: CVE-2026-109618 and CVE-2026-109619. Both are rated CVSS 9.2 and allow code execution on the server without authentication. The fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Will my host update PHP by itself?

Hosts usually update the minor version within a branch themselves, for example from 8.3.35 to 8.3.36. But they can't move a site from 8.1 or 7.4 to 8.3 without your decision, because that may break the site. So it's worth checking which version you actually have.

How much does it cost to update PHP on a site?

An update to the fixed build is from $25 per hour. Moving a WordPress brochure or corporate site to PHP 8.3/8.4 turnkey, with a backup, a test staging site and 48-hour monitoring, is $50. We quote online stores and sites on custom code after a free check.

Will my site break after a PHP update?

It can, if it has old plugins, a legacy theme or modifications. That's why we first update a copy on a test staging site, fix the errors there, and only then change the version on the live site.

My site shows a "critical error" after the update. What should I do?

The fastest way is to switch back to the previous PHP version in your hosting panel, if it's still available, and not touch the site further. Then find the plugin or file that crashes in the error log and replace or fix it. We can take this on the same day you contact us.

How quickly do you reply?

Within an hour during business hours. We check the PHP version and risks about 15 minutes after we receive your site address.

Which PHP version should I choose: 8.3 or 8.4?

For most WordPress sites 8.3 or 8.4 are optimal right now: both are supported and both received the php2shell fix. We make the final call after testing on staging, because it all depends on whether your plugins and theme support that version.
07

Useful from the blog

PHP updates for WordPress and other sites

Updating PHP on a site is usually requested in two cases: the host warned that the old version is no longer supported, or a critical vulnerability came out, like php2shell in October 2026. In both cases the right order is the same: backup, testing on a copy, switch-over and monitoring. That is exactly how we work, and we take on everything that surfaces on the test staging site.

How to update PHP in WordPress

Technically, the version is changed in the hosting panel in a minute. But WordPress doesn't check whether your plugins and theme are ready for the new version. So first update the core, plugins and theme, then test the site on a copy with the new PHP, and only after that switch the live one. If you have no access to a copy, the minimum is a fresh backup and readiness to roll back to the old version immediately.

What happens if you don't update PHP

The site will keep working, and that is the trap. Vulnerabilities like php2shell need no login and no mistake on your side; it's enough that the server accepts requests. The consequences of a hack — malicious code, ads for other people's sites, blocking by Google and by email providers — cost far more than an hour of work today.

We'll check your site in 15 minutes

Send us your site address. We'll tell you the PHP version, whether the site is vulnerable and what needs to be done. Free and with no obligation.

Check my site