Critical PHP vulnerabilities (PHP2Shell): what it means for your website
In October 2026 the PHP project fixed two critical flaws that let an attacker run their own code on a web server without logging in. PHP runs most small business websites, including almost every WordPress site, so if your site has a contact form, a shop or a login, this one matters. WaTo hosting is already patched.
Last updated
The short answer
CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell, are critical flaws in PHP itself that can let an attacker run code on a web server without a password. Fixed releases came out on 21 October 2026: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The Australian Cyber Security Centre has issued an alert. Websites hosted by WaTo are patched. If your site is hosted elsewhere, ask your host to confirm the fix, then change any passwords and API keys stored on the site.
What the flaws are
PHP is the programming language most websites run on behind the scenes. These two flaws are in PHP itself, not in WordPress or a plugin, so a site can be fully up to date and still be exposed if the server's PHP isn't patched. One corrupts memory when PHP runs short of it. The other lets leftover data from one visitor's request be misused in the next. Either can be used to take over the site's files.
Who's affected
Any website running PHP
WordPress, WooCommerce, Joomla, Drupal, Magento and custom PHP sites all run on it.
Every common server setup
Apache, LiteSpeed, PHP-FPM and the rest. The PHP project says every installation that serves web pages is at risk.
Older PHP versions
PHP 8.1 and older get no official fix. Sites still running them should move to a supported version.
Sites that hold keys
Sites that store payment or API keys, such as Stripe, PayPal or email sending keys. A break-in can expose those keys.
Who this is for
- Business owners whose website runs on WordPress or another PHP system.
- Anyone who got a warning about PHP from Stripe, a payment provider or their host.
- Web designers checking client sites on shared hosting.
What to do now
- Confirm the fix with your host. Ask whether PHP on your server has the October 2026 update. On shared hosting you can't patch PHP yourself. The host has to.
- Move off old PHP. If your site runs PHP 8.1 or older, switch it to 8.2 or newer in your hosting panel, then check the site still works.
- Change your keys. Patching closes the hole but doesn't undo a break-in that happened before it. Change your passwords and roll any payment or API keys stored on the site.
- Look for signs of trouble. Check for files you didn't add, new admin users, and charges, refunds or payouts you don't recognise in your payment dashboard.
How WaTo can help
- Our hosting servers are patched for both flaws. Current advisories are on our server status page.
- We'll check a site hosted elsewhere and tell you plainly whether its PHP is exposed.
- We can move your site to patched hosting and help you change keys safely.
PHP vulnerability questions
Is my website affected?
If it runs on PHP and the server hasn't been updated since 21 October 2026, probably. WordPress, WooCommerce and most cPanel hosted sites run on PHP. Your host can tell you which version you're on.
Is WaTo hosting patched?
Yes. Our hosting servers are patched for CVE-2026-109618 and CVE-2026-109619. The server status page lists current security advisories.
Will updating WordPress fix it?
Keeping WordPress updated is always worth doing, but it won't fix this. The flaw is in PHP on the server, so the host has to patch it.
I got an email from Stripe about PHP. What should I do?
Stripe sends these when a site looks like it runs an unpatched PHP version. Get the server patched first, check your Stripe request logs for anything you don't recognise, then roll your API keys. If we host your site, call us and we'll go through it with you.
What if my site is on PHP 7 or 8.0?
Those versions have no official fix. Move to PHP 8.2 or newer. If the site breaks on a newer version, that's a sign it needs work anyway, and we can help.
How WaTo can help with this
Guides on this topic
- What to do if you've been hacked
- cPanel and WHM login bypass (CVE-2026-41940): what it means for your hosting
- Why keep WordPress updated
Sources & references
WaTo Consulting. Last reviewed 2026-10-23. Review when the PHP project or the government updates the advisory.
Not sure if your site is patched?
Give us a call and we'll check your hosting and tell you straight.
Mon to Fri, 8:30am to 5pm




