Two critical vulnerabilities were found in PHP this October under the name PHP2Shell. WordPress, Drupal and Joomla all run on PHP, so this concerns nearly every site built on those platforms. The official security releases came out on 21 October.
Most hosting providers have patched their systems already. That does not mean every site is protected. Here is how to check where yours stands.
What actually happened
PHP is the programming language that runs your site on the server. Because WordPress, Drupal and Joomla are all built on PHP, any flaw in PHP itself reaches straight into the sites built on them.
The two flaws are tracked as CVE-2026-109618 and CVE-2026-109619, and the PHP security team rated both 9.2 out of 10. They let an attacker run their own code on the server without logging in anywhere. From there they can change the content of the site, plant a backdoor on the server, or read passwords and API keys out of memory.
The attacks have already started. Amazon Threat Intelligence caught the first attempt on 17 October, four days before the patches were published. On 26 October CISA added both flaws to its list of vulnerabilities exploited in the wild. The Netherlands temporarily took the national DigiD and MijnOverheid services offline as a precaution.
Updating WordPress is not enough
The flaw is not in WordPress or in its plugins. It is in PHP. A WordPress dashboard can report that everything is up to date while the server underneath still runs a vulnerable PHP version.
Only a PHP upgrade on the server closes it. The patched versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Some providers have backported the fix to older branches as well.
Who has to do that upgrade depends on how the site is hosted.
Shared hosting versus your own server
On shared hosting, the provider is responsible for PHP updates. Many of them patched immediately after the disclosure, and some also fixed older PHP versions that are no longer officially supported. Your site is most likely protected already, but it is worth confirming.
On an unmanaged virtual server (VPS) or a dedicated server, the upgrade is your job. The provider has no view of what software runs inside your machine, and nobody else is going to update it for you.
Keep in mind that patching an old PHP version is a temporary relief. Even if the provider did that extra work for you this time, it may not do it for the next vulnerability.
Who should act now
- Anyone running an unmanaged VPS or their own server. Nobody else updates PHP for you.
- Sites on PHP 8.2 or older. PHP 8.2 gets official security fixes only until the end of 2026, and 8.1 and older are unsupported.
- Sites on cheaper foreign hosts, especially if the provider has sent nothing about PHP2Shell.
- Sites whose developer disappeared years ago and nobody knows exactly how the server is configured.
How to check your PHP version
- In WordPress: Tools → Site Health → Info → Server. The PHP version is listed there.
- In the hosting control panel: the PHP version is visible, and changeable, under the web server settings.
- Ask the provider directly: "Which PHP version does my site run, and does it include the PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619)?"
The version number alone does not always tell the whole story, because some providers patch older branches without changing the number.
Changing the PHP version is often one click in the control panel, but test the change first. Old themes and plugins can break on a newer PHP, especially across a big jump such as 7.4 to 8.4.
Do not fall for "fix plugins"
No WordPress plugin can patch PHP itself, because the plugin runs on PHP. Anything that claims to repair PHP2Shell is useless at best and malware at worst. The same goes for the "test scripts" circulating online: security firm Tenable warns that unverified exploit code is sometimes laced with malware.
A free PHP2Shell check
Tuumpiksel will check your site for free, wherever it is hosted. We find out which PHP version the site runs, whether the security fixes are in place, and whether you need to do anything.
If the site needs an update, we upgrade PHP and test the theme and plugins on a staging copy first, so the live site keeps running without interruption. If we have no access to the server, you get precise instructions for what to ask your provider.
Some sites run on PHP so old that upgrading would mean rewriting most of the theme. In that case we calculate the price of a new site as well. We build with Nuxt and Next.js (Payload CMS), neither of which uses PHP.