PHP2Shell: is your website affected by the PHP vulnerability?
Two critical flaws in PHP threaten millions of websites, and the first attacks are confirmed. How to test whether your website is affected, and what to do now.
Christopher De La Garza · 23 October 2026 · updated 29 October 2026 · 7 min
On 21 October 2026 the PHP project released security updates for two critical vulnerabilities that have become known as PHP2Shell. They allow attackers to run their own code on a web server without logging in. Germany’s Federal Office for Information Security (BSI) rated the situation at warning level 3 (orange), and cities such as Mainz and Potsdam as well as Berlin’s Charité hospital took their websites offline as a precaution.
As a business owner, one question matters: does your website run on PHP, and is it already protected? Here is how to find out and what to do now.
Update 29 October: attacks confirmed
Since 26 October the US cybersecurity agency CISA has listed both flaws in its catalogue of vulnerabilities known to be exploited. A security researcher running decoy servers with PHP 8.4.26 observed attackers executing their own code. At the same time, the search service Censys still counted more than four million PHP installations with a vulnerable version number in Germany alone. The figure is only an indication, because some servers have backported the fix to older versions. But it shows that many websites are still not protected.
That changes the question. It is no longer enough to know whether the update has been installed by now. It matters just as much whether someone used the flaw in the days before.
What happened
PHP is the programming language behind a large part of the internet: behind WordPress, Joomla, many online shops and countless custom applications. The two vulnerabilities (CVE-2026-109618 and CVE-2026-109619) sit in the core of the language. They strike before any of your website’s own code runs, so a plugin or firewall inside WordPress cannot stop them.
What makes it worse: details of the flaws leaked one day before the updates were released. Attackers had a head start, and anyone still running an old PHP version is an easy target. The vulnerabilities are fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older no longer receive updates from the PHP project itself.
Are you affected? Test it with three questions
1. Does your website run on PHP? It does if it is built with WordPress, Joomla, TYPO3, Shopware, WooCommerce or a similar system. A static website, delivered as finished pages, is not affected. If you are unsure, the answer is usually: yes, PHP.
2. Who looks after the server? This is the decisive difference. With classic web hosting or managed hosting, the host installs the updates. Many did so on 21 and 22 October. If you rent your own server, a so-called dedicated or cloud server, you are responsible yourself. That is exactly what hosts are pointing out by email these days.
3. Which PHP version is running? You will find the version in your host’s customer area, usually under “PHP settings”, or in WordPress under Tools, Site Health, Info, Server. Anything below the versions above is unprotected, unless your host has backported the fix.
What you should do now
- Read your host’s status page. Most hosts report there whether and when they patched. If there is nothing, ask support.
- Check and update your PHP version. If you are still on PHP 8.1 or older, now is the moment to move to a current version. Make a backup first.
- Update WordPress, your theme and plugins. They don’t close the PHP flaw, but attacks rarely come alone. Old plugins are the second open window.
- Watch for warning signs. Unknown admin accounts, new files on the server, redirects to other sites or spam sent in your name are red flags. Then change passwords and have the website checked thoroughly.
- Keep a backup. A current backup stored outside the server is the fastest way back in an emergency.
Why an update is often not enough
The update itself is installed quickly. The effort lies elsewhere, as security researchers also stress: first you need to know everywhere PHP is running, such as an old second site, a shop or a forgotten test environment. Then older plugins and themes often don’t work with a new PHP version, and the website breaks after the update. And finally there is the question of whether someone used the flaw before it was closed.
Small businesses are hit hardest. Often a single person looks after the website on the side, or nobody does any more since the agency from back then can no longer be reached.
Beware of scam emails
Wherever a vulnerability makes headlines, scammers are not far behind. Expect emails in the coming weeks that claim to come from your host and ask you to log in via a link or to pay for a “security update”. Reputable hosts never ask for passwords by email. If in doubt, always log in directly via your host’s website, not via a link in an email.
How we handle it at NEOPAQ
The websites we run on our own server in Germany don’t use PHP. They are delivered as finished, static pages, so there was nothing to attack for this vulnerability. WordPress websites in our maintenance are hosted by a specialist hosting partner that installed the updates on 21 October.
That is no coincidence but the reason we take maintenance so seriously. A website is never simply finished, more on that in Website maintenance: why “finished” doesn’t exist.
Sources: PHP security advisory of 21 Oct 2026, Hetzner status report, heise online: successful attacks confirmed, 27 Oct 2026 (German), tagesschau.de: vulnerability threatens websites worldwide (German), tagesschau.de: interview on the consequences for businesses (German).
Frequently asked questions
How can I test whether my website is affected by the PHP vulnerability?
Clarify three things: Does the website run on PHP (always the case with WordPress, Joomla, TYPO3 or Shopware)? Which PHP version is running (in your host's customer area, or in WordPress under Tools, Site Health)? And has your host installed the fix? PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 or newer within the same series are protected, unless your host has backported the fix. If you'd rather not check yourself, we check your website from the outside for free and tell you whether anything points to a risk.
What should I do if my website has already been attacked?
Don't just let it keep running. Inform your host, change all passwords (hosting, WordPress, database, FTP) and have someone look for unknown users and files. If in doubt, restore a clean backup from before 20 October and update straight away. If customer data is affected, you may have to notify the data protection authority within 72 hours of becoming aware of it.
Is every WordPress website affected?
Every WordPress website runs on PHP. It is protected as soon as the server uses a fixed PHP version. With managed hosting that has usually happened already; on your own server you have to act yourself.
My host says everything is done. Do I still need to do anything?
Not for the PHP flaw itself. Still check that WordPress and plugins are up to date and that you have a backup.
How can I tell whether my website has already been attacked?
Typical signs are unknown users, sudden redirects, foreign content or warnings from Google. If these signs are missing, that doesn't guarantee nothing happened. If in doubt, a check is worth it.
Are visitors to my website at risk?
Not directly. But if a website is taken over, attackers can steal customer data there or redirect visitors to dangerous sites.
What does your security check cost?
Nothing. We check your website from the outside, without passwords or access, and send you within one working day what we noticed and which questions to ask your host. Only if there is something to do will you get a quote, if you want one.
Free security check
We check your website from the outside and tell you within one working day whether anything points to a risk and what you should do now. No passwords, no access.
Check my website