PHP2Shell isn’t a WordPress bug — it’s a flaw underneath almost every business website, and it lets a stranger take over the web server without a password. Updated WordPress last week? That doesn’t fix this one — and the site your agency built in 2019 probably isn’t patched at all.
- Two critical flaws in PHP itself — CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell — let an attacker run code on a web server without logging in.
- Almost every PHP version since 5.4 (2012) is affected — so WordPress, Joomla, Drupal, Magento, Laravel and most cPanel-hosted sites are exposed until PHP is updated.
- Updating WordPress does not fix it. Only updating PHP does.
- Patches landed 21 October 2026 (PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35). ASD’s ACSC issued a critical alert the same day.
- Attack attempts were seen days before the patch. Check your PHP version today — or ask whoever hosts your website.
What is the PHP2Shell flaw?
PHP2Shell is two critical vulnerabilities in the PHP language itself, disclosed in October 2026 — not in WordPress, and not in any one plugin. PHP is the language most websites are built on. Both vulnerabilities allow unauthenticated remote code execution: a stranger can make your web server run their instructions, with no password and no login. The fix is a single update, applied to PHP itself — not to your website.
The two vulnerabilities were found by Wiz Research with help from large language models, and demonstrated against current WordPress, Drupal and Joomla sites. The PHP Foundation’s security team rated both at CVSS v4.0 9.2, and every PHP release back to version 5.4 (2012) is affected until the host updates PHP.
How it works, in plain English
PHP’s emergency security release on 21 October 2026 closed two vulnerabilities. You don’t need the internals, but the shape matters. In one flaw, out-of-memory handling can interrupt PHP while internal request data is only partially built, and request cleanup then treats that invalid data as valid. In the other, request-owned internal state survives after its backing memory has been freed, and a later request handled by the same worker reuses that stale state before normal initialisation resets it. Both happen before your website’s own code runs — so how well your site is built makes no difference.
WordPress, cPanel and every other portal
PHP2Shell is not a WordPress problem — it’s an “everything built on PHP” problem. WordPress, Joomla, Drupal, Magento, Laravel, client portals, booking systems and other PHP sites are all exposed while the host runs an unpatched PHP version. WordPress.org has confirmed no WordPress update is planned, because the fix isn’t in WordPress — it’s the PHP version your host runs.
| You run… | Exposed? | What fixes it |
|---|---|---|
| WordPress / Joomla / Drupal / Magento on a host | Yes, if PHP isn’t updated | Host updates PHP — get it in writing |
| cPanel server, PHP 7.4–8.5 | Yes, until patched | Apply EasyApache 4 (ea-php) updates |
| cPanel on PHP 7.3 or older (no CloudLinux), or CentOS 7 | Yes — no patch coming | Upgrade PHP / migrate the server |
| Laravel or custom PHP app | Yes | Update PHP on the server |
| Fully hosted SaaS (Shopify, Squarespace, Wix) | Provider’s job | Check their status page |
cPanel ships updated builds through EasyApache 4, with backports to PHP 7.4, 8.0 and 8.1. But PHP 7.3 and older without CloudLinux, and anything on CentOS 7, get no fix at all — those boxes must be upgraded or moved. The real risk is the sites nobody remembers: the agency-built site from 2019, the portal from a business you acquired. If nobody owns it, nobody updated it. September brought a separate critical WordPress core flaw too (CVE-2026-87902) — two critical holes in one month.
“When we take on a new client, the website they tell us about is rarely the only one they own. We’ll find an old WordPress or a client portal still sitting on a PHP version that went end-of-life years ago — and everyone assumed someone else was keeping it patched. Nobody was.”— PIP, on what new-client audits turn up
What it means for Australian businesses
ASD’s ACSC issued a critical alert on 21 October 2026, telling organisations to find all PHP installations across their internet-facing systems, apply the security updates, and watch for suspicious activity. Report incidents on 1300 CYBER1 (1300 292 371). Overseas, several governments took whole web estates offline to update.
A compromised website can leak customer data, and Wiz showed the vulnerability can expose passwords, tokens and API keys held in memory. If personal information is accessed, the Notifiable Data Breaches scheme under the Privacy Act 1988 may apply — if you think you’ve been hit, start with incident response. Your website is usually wired to CRM forms, payment gateways, email and Microsoft 365, so a takeover is a foothold into all of it. Keeping internet-facing systems current is an ASD Essential Eight control — patching applications is expected within 48 hours when a critical flaw is actively exploited.
How to check and update your PHP version
The one rule that matters: WordPress can’t update PHP itself — only your host can.
Site Health → Info
In the dashboard go to Tools, then Site Health, then the Info tab, and open the Server section to read your PHP version. Compare it to the fixed versions below — if your PHP version is lower, ask your host to update it.
MultiPHP Manager
Open MultiPHP Manager in cPanel (or WHM for server admins). Confirm the EasyApache 4 updates are actually applied — selecting a version number alone does not install the security patch.
Ask, in writing
Email your host or IT provider today and ask for written confirmation that PHP was updated to a fixed version after 21 October 2026. “It’s handled” is not confirmation.
PHP released 8.5.12 · 8.4.27 · 8.3.36 · 8.2.35 on 21 October 2026 (or run a vendor backport). PHP 8.2 security support ends 31 December 2026 — plan the next upgrade now.
Temporary mitigations — config tweaks and WAF rules from Cloudflare and others — reduce exposure but are not complete mitigations. Updating is the only safe choice. Avoid unverified “fix” plugins and copy-pasted snippets — some do more harm than the vulnerability.
Signs you may already have been hit
Patching closes the door, but it doesn’t evict anyone already inside. None are proof alone, but together they warrant a closer look: repeated HTTP 500 errors or memory-limit errors after unusual upload requests, oversized or malformed PHPSESSID cookies, unexplained PHP worker restarts, admin users you don’t recognise, new files in upload folders, or plugins you never installed. If you see them, treat it as compromised: update, then rotate every credential it held — database, API keys, email passwords. A security audit confirms what’s exposed before an attacker does.
How it unfolded
Common questions
Is the PHP vulnerability fixed?
Do I need to update PHP if I’ve already updated WordPress?
Where do I find my PHP version in WordPress?
How do I update the PHP version in cPanel?
Not sure what PHP version your website is running?
PIP checks web servers, hosting and every PHP application your business relies on — including the ones nobody remembers. Find out what’s exposed before an attacker does.
Book a security audit →
