Guide · AT-R35REV. 2026-A
PHP2Shell: is your website affected by the PHP vulnerability?

By Jordan WichertSenior backend developerLast updated:
As of 22.10.2026, checked against the security announcement on php.net and the warning from the BSI (German Federal Office for Information Security). The situation is changing from day to day.
What happened
PHP is the programming language that a large share of all websites run on. It works on the server, not in your visitors' browser. The two flaws (CVE-2026-109618 and CVE-2026-109619) are in PHP itself, one layer below WordPress or your shop. All PHP versions from 5.4 onwards are affected, in every usual way of running it on a web server. An attacker does not need an account on your site for this.
The details were meant to become public only with the update. First details leaked on 20 October, a day early. Amazon observed an attack attempt as early as 17 October, and since the 21st several security firms have reported attacks in progress. Authorities in the Netherlands, France and Finland took sites offline as a precaution until the update was installed. The BSI issued a warning on 21 October.
Is your website affected?
That depends on what it runs on and who operates the server.
- WordPress, Joomla, TYPO3, Contao, Shopware or WooCommerce at a web host: affected as long as an old PHP version is running there. The host installs the update on the server, not you.
- Your own server, meaning a rented virtual server or a computer on your premises that runs PHP (for example for your own Nextcloud): here you are the host yourself. More on this below.
- Website builders such as Wix, Jimdo or Squarespace: the provider operates the server. You cannot update anything there and do not need to.
- Static website made of finished HTML files: the server does not run PHP, so the flaw does not apply. With one caveat that is often overlooked.
The caveat is the forgotten installation. On many web hosting packages there is more than the actual website: the test copy from back then under /alt or /test, an old form script, an image gallery from the 2010s. If PHP runs there, that too is an entry point, because an attacker needs just one file that PHP executes. The host closes the flaw for all these folders too, but only in the PHP versions it has actually fixed. If the old test site is still on PHP 7.2, for which there is no fix, it generally stays open.
How to find out your PHP version
In WordPress it takes a minute: in the menu on the left click Tools, then Site Health, and at the top the Info tab. Under Server you will find the PHP version. For other systems, and to see all domains at once, look in your host's customer menu, usually under an item such as “PHP version” or “PHP settings”. There you can also see whether individual domains or subfolders use a different version.
These versions and everything after them are safe:
| Series | Fixed from |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
| PHP 8.1 and older | no update from the PHP project |
There is a caveat here too. Some servers receive the fix as a package from their Linux system. There the version number often stays the same even though the fix is included. An older number therefore does not mean for certain that the flaw is open. It means you need to ask.
What your host must do and what to ask
With rented web hosting, the update is the host's job. It must bring PHP to a fixed version and then restart the running PHP processes. Only then is the old code really out of memory. Whether this is done is often stated on its status page or in an e-mail to customers. If nothing specific is there, write briefly to customer service, for example:
- Is PHP on my package now running in a version that fixes CVE-2026-109618 and CVE-2026-109619?
- Does this apply to all PHP versions I can select in my package, including the older ones?
- When exactly was the update installed? (You need the date for the next step.)
Is your site still on PHP 7.4, 8.0 or 8.1?
Then you have the real problem. For these series the PHP project does not release a ready-made update, only fixes in the source code for anyone who builds PHP themselves. Some hosts and Linux vendors provide such fixes. You should not rely on it. For everything before 7.4 there is nothing at all any more.
The way out is to switch to a current series. With most hosts this is a selection field in the customer menu, and the click is quick. The risk lies elsewhere: old plugins and themes that have not had an update for years sometimes no longer run on new PHP. The site then shows a white screen or an error message. So, in this order:
- Take a full backup, files and database. Many hosts offer this in the customer menu.
- Update WordPress, theme and plugins. Replace or remove anything that is no longer maintained.
- Only then switch the PHP version and click through the site: home page, contact form, the checkout if there is a shop.
- If the update breaks something, you can switch back in the same menu. Treat that as a stopgap for a few hours. The old version is still vulnerable.
Use at least PHP 8.3, preferably 8.4. PHP 8.2 has a fix, but it reaches end of life on 31 December 2026 and will receive no more security updates after that. If you are upgrading now, a newer version saves you from having to switch again in ten weeks.
After the update: check whether anyone got in
The update closes the door. It does nothing about anyone who came in beforehand. So you should check the period from 17 October, the day of the first observed attack attempt, and not only from the update. On a WordPress site you can check a good deal yourself:
- Under Users: are there administrators you do not know?
- Under Plugins: is there anything that none of you installed?
- Does the site redirect visitors to unfamiliar addresses? This often happens only on mobile or only for people arriving from a Google search.
- When you search for your domain, does Google show pages that do not exist on your site? Spam in English or Japanese is the classic.
However, a skilled attacker leaves none of these traces. Inconspicuous does not mean clean. If you want to be sure, have the files on the server compared with a backup from before 17 October, or with the original packages of WordPress and the plugins.
After that, and really only after that, change the passwords. Anyone who could run PHP on your server could reach everything stored there: the database password from the configuration file, the WordPress administrators' logins, the FTP or SFTP access and the keys stored in plugins (mail sending, payment providers, interfaces to inventory management). If you change them before the update, you hand the new passwords straight to an attacker who is still inside.
And one more thing that is easily forgotten: do not delete any backup from before 17 October now. Many backups rotate and discard the oldest after 14 or 30 days. If it turns out in three weeks that someone was in after all, that very copy is the one most likely to be clean. How a backup should be structured is explained in the guide on the 3-2-1 rule.
Own server, Nextcloud or admin panel
Anyone who runs PHP themselves, on a rented virtual server, a server on their premises or for their own Nextcloud, is their own host. The task is then: update the packages, restart PHP-FPM or Apache, and check that the fixed version is really running. The major Linux distributions received the fixes in advance; whether your package contains them is stated in your distribution's security announcement. The version number alone does not tell you (see above).
If PHP runs in a container, it is inside the image. A restart is then not enough: the image must be pulled again or rebuilt. Admin panels such as Plesk or cPanel and some devices bring their own PHP, so the update comes from the manufacturer.
Until the update is running, the PHP project lists settings that reduce the risk, among them:
session.upload_progress.enabled = 0The full list is in the security announcement on php.net. The PHP project itself says: only the update gives full protection.
What you can do yourself
Most people can check the version and ask their hosting provider themselves, at no cost from us. We usually help when upgrading a site still on PHP 7.4 or 8.1 breaks its plugins, or when nobody has the hosting credentials any more. That happens more often than you might think if someone else built the site years ago. Get help if you see signs of a compromise. Our hourly rate is listed on the prices page.
Common questions
Is it enough to update WordPress and the plugins?
No. The flaw is in PHP, one layer below WordPress. A WordPress update changes nothing in PHP. You should still keep WordPress up to date, especially if you are switching PHP version now.
Does a security plugin or maintenance mode protect me?
No. Both run in PHP themselves and only come into play once PHP has already accepted the request. The flaw lies before that. If you want to take the site offline temporarily, do it at the host, for example by switching PHP off for the domain.
Does Cloudflare help?
To a degree. Cloudflare has set up filter rules against the known attack routes, including on the free plan. But they only apply to requests that actually pass through Cloudflare. If your server can also be reached directly, an attack bypasses them. Cloudflare itself calls it a stopgap.
Should I take my website offline as a precaution?
If your host cannot confirm that the update has been installed: yes. Authorities in several countries took their sites offline in exactly this way until the update, and the IT emergency team of the EU institutions (CERT-EU) and the British cyber security agency advise it. Taking it offline here means: at the host, not with a plugin.
Is this website affected?
No. aureum-tech.com is built with Astro. The server delivers finished files and does not run any PHP while doing so. This is also how we build new websites for our clients.