PHP2Shell vulnerability: should your SME update PHP on its website?
Back to the blog
News

PHP2Shell vulnerability: should your SME update PHP on its website?

Jérémy
Jérémy
Founder & CTO
21 October 20266 min read

Two critical PHP vulnerabilities, known as PHP2Shell, were fixed on 21 October 2026. How to tell whether your website is affected and what to ask your hosting provider.

If your website or app runs on PHP, yes, you need to update PHP now. On 21 October 2026, the language's team released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical vulnerabilities, grouped under the name PHP2Shell. They allow an attacker to run code on the server without needing to log in. The good news is that the fix already exists and can usually be applied without touching your website's code.

WordPress, Drupal, Joomla, PrestaShop, Symfony, Laravel and Sulu all rely on PHP. Many SMEs therefore use PHP without knowing it, sometimes also in an internal tool or an admin interface. Here is how to tell whether you are affected and what to ask your agency or your hosting provider.

What happened with the PHP2Shell vulnerability?

On 20 October, the PHP team announced an urgent security update for the following day. On 21 October, it published its official security advisory on php.net. It describes two vulnerabilities rated 9.2 out of 10 (CVSS 4.0), the critical level.

  • CVE-2026-109618: when PHP runs out of memory at the wrong moment, for example while a file is being uploaded through a form, the request clean-up can handle improperly initialised data. An attacker can take advantage of this to run their own code.
  • CVE-2026-109619: some internal information from a request can survive after a fatal error. The next request handled by the same process may then reuse it, which here too opens the door to code execution.

According to the PHP team, every installation that answers web requests is exposed: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The highest risk concerns mod_php, for which a demonstration shows that a single anonymous request is enough to trigger the attack, before the website's code even runs.

How can I tell whether my website is affected?

The question to ask is simple: does your website, your online shop or your business tool run on PHP? If you use a CMS such as WordPress, the answer is almost always yes. For a custom-built website, the person who built it will tell you in a minute.

Switzerland's National Cyber Security Centre stresses one point in its alert of 21 October: you should not look only at the public website. PHP can also run behind an admin interface, an internal application, a hosting platform or a network device, without the company knowing.

How do I check my website's PHP version?

There are several ways, depending on your setup:

  • In WordPress, the Tools menu then Site Health, Info tab, shows the server's PHP version.
  • With most shared hosting providers, the customer area shows the PHP version of each hosting plan and often lets you change it.
  • On a server you manage, the php -v command gives the version installed for the command line. Also check the one that actually serves the pages, which may be different.

A version equal to or higher than 8.5.12, 8.4.27, 8.3.36 or 8.2.35 on its branch is fixed. Watch out for one trap: Linux distributions often apply the fix under their own package number. A server may therefore show an older number while being protected. In that case, the distribution's security bulletin is what counts.

What if my website still runs on PHP 8.1 or PHP 7?

The PHP project no longer releases updates for PHP 8.1 and earlier versions. Some distributions and extended support providers nevertheless offer a fix, and the PHP team has supplied minimal patches for PHP 7.4, 8.0 and 8.1 for those who compile it themselves. It is a stopgap. The real answer is to move to a maintained version.

This move sometimes requires adapting the code, especially for an old website or a module developed several years ago. It is often the right time to take stock of the tool, as we explained in our article on the cost of custom software for an SME. Note also that PHP 8.2 will no longer receive security fixes after 31 December 2026.

What should I ask my agency or my hosting provider?

You do not need to do the update yourself. You can, however, ask for written confirmation. Here are the questions we would ask in your place:

  • Which PHP version currently serves my website, and is it fixed against CVE-2026-109618 and CVE-2026-109619?
  • Have the PHP processes been restarted after the update? Without a restart, the old version may keep answering.
  • Have my other PHP tools (back office, extranet, internal application) been checked as well?
  • Do the server logs show unusual requests, crashes or modified files in recent days?

This last point matters. As the Swiss centre points out, an update closes the vulnerability, but it does not erase an intrusion that may already have happened. If your website is hosted on a dedicated server or a VPS, someone also needs to rebuild the containers where relevant. This is one of the advantages of automated hosting and deployment, where a new image is redeployed in a few minutes.

What if the update cannot be done right away?

The PHP team describes temporary settings, such as disabling the file upload progress bar (session.upload_progress.enabled) or limiting request size. It states that they reduce some attack paths without making the installation safe. They can also break forms or document uploads. For a business website, we keep them for a few hours of transition, while the real fix is applied.

If a sensitive tool really cannot be updated, the Swiss centre advises restricting access to only the people who need it, or even disconnecting it from the internet temporarily.

Why is a small business a target too?

An attack like this does not target a particular company. Bots scan the internet looking for servers that have not yet been updated, whatever the size of the company behind them. It is the same logic as in the attack on supermarkets' connected fridges. The least monitored link is the first to give way.

For your own tools, security depends as much on follow-up as on development. When we design custom software, we plan from the outset who monitors security advisories and how quickly fixes go into production. On the same subject, our article on passkeys and the “123456” password leak shows how to protect access to these tools.

Not sure which PHP version runs your website, or want a quick check of your tools? We are in Rumilly, near Annecy, and we will look into it with you, without jargon.

So you no longer have to keep track of these updates yourself, our maintenance service includes hosting, backups and security updates. We explain what a website maintenance contract covers.

Frequently asked questions

What is the PHP2Shell vulnerability?

It is the name given to two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026. Rated 9.2 out of 10, they can allow an attacker who is not logged in to run code on a server that runs PHP for a website or web application.

Which PHP versions fix the vulnerability?

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. On Linux, the distribution may also apply the fix under its own package number: in that case, rely on its security bulletin. For PHP 8.1 and older versions, you need a fix supplied by a provider or, better still, to move to a maintained version.

Is my WordPress website affected?

WordPress runs on PHP, so the server hosting it is affected until it is patched. It is not WordPress that needs updating here, but PHP itself. You can see the version under Tools, Site Health, then ask your hosting provider to confirm the fix.

Can updating PHP break my website?

Moving to the latest version of the same branch, for example from 8.3.35 to 8.3.36, in principle only brings fixes and rarely causes problems. Moving from an old version such as PHP 7.4 to PHP 8.x is a real change, which requires testing the website and sometimes adapting the code.

How can METEORA help me with this PHP vulnerability?

We check with you which PHP version runs your website and your tools, whether the fix has been applied and whether the processes have been restarted. If an upgrade is needed, we tell you what it involves before touching anything. We are based in Rumilly, near Annecy.

PHPCybersecuritySecurity vulnerabilityHostingSMEWordPress

How much would your project cost?

Project type, features, timeline: a costed estimate in two minutes, with no commitment.

Estimate my budget

Is your website up to date?

From Rumilly, near Annecy, we check the PHP version of your website and your business tools, then tell you clearly what still needs fixing.