Blog / Company News / PHP Vulnerability 2026: what it means for your WordPress site
(last updated: )

PHP Vulnerability 2026: what it means for your WordPress site

A critical PHP flaw called PHP2Shell can put WordPress sites at risk. Here is what happened in plain language, whether your site is affected, and the quick steps to update PHP and stay protected.

7 min read

In short. PHP2Shell is a pair of critical PHP flaws (CVE-2026-109618 and CVE-2026-109619) that let attackers run code on a server without logging in. Every PHP site is in scope, and WordPress is the most common example. PHP fixed the flaws on October 21, 2026, and another security release is due November 19.

If your website runs on WordPress, it runs on PHP, so a flaw in PHP sits right underneath your site. The same goes for any other PHP-based site. The good news is that the fixes exist and applying them is quick. This guide explains what happened in plain language and what to do about it, with a focus on WordPress.

What does PHP stand for, and what is PHP used for?

PHP stands for “PHP: Hypertext Preprocessor”, a self-referencing name that began life as “Personal Home Page”. It is a programming language that runs on a web server and builds each page on demand, which is why it powers about 70% of the sites whose server-side language is known. WordPress is written in PHP, so every time a visitor loads one of your pages, PHP is the engine doing the work.

What is the PHP vulnerability?

The PHP vulnerability behind the 2026 headlines is called PHP2Shell, a pair of flaws in the core of PHP that let an attacker run commands on a server without logging in. The two bugs are CVE-2026-109618 and CVE-2026-109619, and both are rated critical with a CVSS v4.0 score of 9.2. The first involves how PHP behaves when it runs out of memory. The second involves leftover data from one request that a later request can pick up by mistake.

Both flaws sat in PHP for more than a decade. Two research teams, Calif and Wiz, found them independently with the help of AI models, and PHP released fixes on October 21, 2026, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Attackers are probing for the flaws, and some real-world exploitation has been reported against network appliances, so there is no reason to wait.

Is WordPress affected by the PHP vulnerability?

Yes, WordPress sites can be affected, because WordPress is built on PHP and the flaws sit in PHP itself, not in a plugin or theme. A typical WordPress vulnerability is a bug in a plugin or theme that you fix with an update from your dashboard. The WordPress PHP vulnerability is different. Wiz demonstrated remote code execution against WordPress, and updating plugins will not close it, because the problem lives in PHP on your server.

Where you host decides who does the update. Contabo does not offer managed hosting, so on a Cloud VPS, Cloud VDS or Dedicated Server the PHP update is yours. If you are not sure your server has the October 21 fixes, check your Linux distribution’s security notice for CVE-2026-109618 and CVE-2026-109619, because a patched build can keep its old version number.

Is only WordPress affected by the PHP vulnerability?

No, every site and application that runs on PHP is in scope, because the flaws sit in PHP itself. The PHP project says all installations serving web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. Wiz also demonstrated code execution against Drupal and Joomla, so other content systems, online shops and custom applications share the exposure. Some network appliances use PHP in their web interfaces too, and attackers have targeted network appliances.

What is the latest PHP news?

PHP scheduled a regular security release for November 19, 2026, between 2:00 and 2:30 p.m. UTC, covering all supported versions. The project rates the highest severity in it as critical, but says the critical issues need a non-default or uncommon setup.

The release is expected to include a fix for CVE-2026-115560, a separate code-execution flaw that only applies when an application switches its session handler in an unusual way and session upload progress is on. As of October 23, no attacks on it had been reported. Until you can update, PHP advises setting session.upload_progress.enabled=0 and restarting your PHP workers.

How to update PHP in WordPress

To update PHP for WordPress on a server you manage, you update the PHP packages on the server itself, because WordPress cannot do it from inside the dashboard. Most sites need four short steps.

  1. Check your current version. In your dashboard, open Tools, then Site Health, then the Info tab, and expand Server. On the server, php -v shows the same.
  2. Back up and update. Take a full backup of your files and database, then update WordPress core, plugins and themes.
  3. Update PHP. Use your package manager, then restart PHP-FPM, or Apache if you use mod_php. An Ubuntu or Debian example follows this list.
  4. Test your site. Load your homepage and log in to wp-admin, then submit a form or run a test checkout.
sudo apt update && sudo apt upgrade
sudo systemctl restart php8.3-fpm

Match the service name to your PHP version, and confirm the fix in your vendor’s notice rather than relying on php -v alone.

PHP 8.1 and older no longer get official fixes, and PHP 8.2 reaches end of life on December 31, 2026. If you are on either, plan an upgrade to a newer branch such as 8.3 or 8.4.

What if something breaks after the PHP update?

Most problems after a PHP update come from an older plugin or theme, and each has a quick fix.

  • White screen or 500 error. A plugin or theme does not support the new PHP version. Rename its folder over SFTP to deactivate it, then update or replace it.
  • Deprecation warnings on the page. Older code uses features that newer PHP flags. Turn off display_errors on the live site and read the log.
  • Site Health still shows the old version. The PHP service may not have restarted. Restart PHP-FPM, clear your cache, and check again.

FAQ

What is a PHP vulnerability?

A PHP vulnerability is a flaw in PHP itself, or in code written in PHP, that attackers can abuse to read data, change content, or run commands on a server. A flaw in PHP’s core, like PHP2Shell, affects every site on that server, whatever application it runs. A flaw in a plugin or script affects only the sites that use it.

Is the 2026 PHP vulnerability being exploited?

Attackers are scanning for PHP2Shell, and some real-world exploitation has been reported against network appliances. Exploit attempts have surged since the flaws were disclosed, so waiting is the riskier choice. Update PHP now. If you cannot, apply the partial interim setting session.upload_progress.enabled=0, restart your PHP workers, and update as soon as you can.

Is my WordPress site safe from the PHP vulnerability?

Your WordPress site is protected against PHP2Shell once its server runs a patched PHP build. Check Site Health or php -v for the version, then confirm the fix in your distribution’s security notice, because a patched build can keep an older version number. Updating plugins alone does not close the flaw, because it sits in PHP on the server, one layer below WordPress.

Is only WordPress affected by the PHP vulnerability?

No. Every site and application running on PHP is in scope, because the flaws sit in PHP itself. The PHP project says all installations serving web requests are at risk, including PHP-FPM, Apache with mod_php and LiteSpeed. WordPress, Drupal and Joomla have all been shown to be exploitable, and attackers have used the flaws against some network appliances, so update every PHP server you run.

How can I improve PHP security on my WordPress site?

Run a supported PHP version and install each security release soon after it ships. Turn off PHP features you do not use, such as session upload progress, and keep WordPress core, plugins, and themes updated. Keep fresh backups so you can roll back if an update causes trouble, and check your distribution’s security notices regularly so you hear about new PHP fixes early.

Share 𝕏 in