The PHP flaw that took government websites offline: what it means for your business website
If you caught the news this week, you’ll have seen government websites in Australia, Europe and Canada going dark. The cause wasn’t a single hack. It was two critical security flaws in PHP, the programming language that quietly runs a huge share of the internet, including most WordPress websites.
Here’s what actually happened, what the headlines got slightly wrong, and the practical steps every business with a website should take this week.
What happened
On 21 October 2026, the PHP project released emergency updates to fix two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed “PHP2Shell”. Both are rated 9.2 out of 10 on the CVSS severity scale, and both can let an attacker run their own code on a vulnerable web server without needing a password or login.
The flaws were found with the help of AI. Several security teams using AI models, including researchers at Calif and Wiz, uncovered the bugs, and the fixes were coordinated with the PHP team before the details went public.
Because PHP is so widely used, cyber security agencies around the world told website owners to patch immediately or take their sites offline until they could. Many governments chose the cautious route:
- Australia: the Australian Cyber Security Centre issued a critical alert, and its own site, cyber.gov.au, was among the government websites affected, along with sites such as the Australian Bureau of Statistics and Jobs and Skills Australia. Some NSW government sites were also taken down temporarily while patches were applied.
- Europe: government sites in the Netherlands, Finland, France and Denmark were taken offline as a precaution.
- Canada: federal government sites went offline following guidance from the Canadian Centre for Cyber Security, and some provincial sites followed.
At the time of its alert, the ACSC said it wasn’t aware of the flaws being actively exploited in Australia. Overseas, security firms including Qualys soon reported exploitation attempts in the wild, and proof-of-concept attack code began circulating within a day of the details going public. In other words: the window between “disclosed” and “attacked” is short.
About that “70%” figure
Some coverage said the flaw affected 70% of government websites. That’s not quite right. The figure comes from web technology tracker W3Techs, which estimates that PHP runs roughly 70% of all websites whose programming language can be identified. It describes how widespread PHP is, not how many sites were knocked offline or breached.
The real point stands, though: if PHP runs most of the web, a flaw in PHP is a problem for most of the web. That includes small business sites, not just government portals.
Is your website affected?
If your website runs on WordPress, it runs on PHP. WordPress powers over 40% of all websites, from blogs and online shops to local trade businesses and professional services, so WordPress security is squarely in the frame. Other popular platforms like Joomla and Drupal also run on PHP.
Your site is potentially exposed if it’s running any PHP version older than these fixed releases:
That last row matters. If your site is still running PHP 8.1, 7.4 or older, there’s no official update coming. PHP has published source-code patches for those old versions, and some hosts and Linux distributions apply them, but you’d be relying on your host to have done that. The safe fix is to upgrade to a supported version. If you’re on 8.2, plan that upgrade now too, because 8.2 stops receiving security fixes at the end of this year.
The businesses most at risk are the ones that don’t know who looks after this. Many small sites sit on cheap shared hosting, where the owner doesn’t manage the server and may have no idea whether PHP is being updated. If that sounds familiar, now is the time to find out.
If your website is built on Shopify, Squarespace or Wix, the platform manages the underlying servers for you, so this isn’t something you can or need to patch yourself.
What to do this week
- Check your PHP version. In WordPress, go to Tools → Site Health → Info → Server. Your PHP version is listed there. Your hosting control panel will usually show it too.
- Ask your host directly. Email or call them and ask: “Have you updated PHP to the 21 October 2026 security release on my server?” Get a yes or no, in writing.
- Upgrade if you’re on PHP 8.1 or older. Test on a staging copy of your site first, because older plugins and themes can break on newer PHP. If you don’t have staging, ask your web developer to do it.
- Make sure the update has actually taken effect. PHP needs to be restarted after patching. Recheck your version in Site Health once your host says it’s done.
- Look for signs of trouble. New administrator accounts you didn’t create, unfamiliar files or plugins, unexpected redirects, or spam pages appearing in Google are all red flags. If you see any, change your passwords and get a professional to check the site.
- Confirm you have a recent backup, stored somewhere other than the website’s own server.
- Update everything else while you’re there. WordPress core, your theme and every plugin. A patched PHP won’t protect a site with a vulnerable plugin.
Think your WordPress site has been hacked?
A hacked WordPress site doesn’t always look broken. Common signs include Google showing spam pages or a “This site may be hacked” warning under your listing, visitors being redirected to other websites, admin accounts you don’t recognise, or your host suspending the site for sending spam.
If you see any of these, don’t just delete the odd file and move on. Take the site offline or into maintenance mode, change every password (WordPress, hosting, database and email), restore from a clean backup taken before the problem started, then update PHP, WordPress, your theme and plugins before you bring it back. If you’re not sure the site is clean, get a professional to check it, because a hidden backdoor will let attackers straight back in.
Questions to ask whoever manages your website
If someone else looks after your site, these five questions will tell you quickly whether you’re in good hands:
- What PHP version is my site running right now?
- Was it updated to the 21 October 2026 security release, and when?
- How do you get notified about critical security issues like this one?
- How often are my site’s backups taken, and where are they stored?
- If my site were compromised, what’s the plan?
If the answer to most of these is “I’m not sure”, that’s your answer.
The bigger lesson: “set and forget” websites are a risk
This won’t be the last flaw of its kind. AI is making it faster to find security holes in widely used software, for defenders and attackers alike. That means more critical updates, arriving with less warning.
A website isn’t a brochure you print once. It’s software running on a server, and it needs looking after. Cheap hosting with nobody watching it is fine right up until the week it isn’t.
Not sure if your site is safe?
If you don’t know what PHP version your website runs, who updates it, or whether anyone checked this week, we can help. Send your website address to hello@krakendigital.com.au and we’ll tell you what version you’re on and whether you’re exposed, in plain English.
For a quick first look, run our free website health check. In about 15 seconds it checks your HTTPS set-up, security headers and whether your site advertises its software version, alongside SEO and speed.
And if it’s time to move to hosting where someone’s actually watching, our WordPress hosting in Australia starts from $690 a year + GST, with Australian data centres and security updates handled for you. For businesses that want the updates, backups and checks done every month, see our website maintenance in Melbourne.
Frequently asked questions
What is PHP2Shell?
PHP2Shell is the nickname for two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) disclosed and patched on 21 October 2026. They can allow an attacker to run code on a web server without logging in.
Does this affect WordPress websites?
Yes. WordPress runs on PHP, so any WordPress site on an unpatched PHP version is potentially exposed. The fix is applied to the server’s PHP, not to WordPress itself.
How do I check my website’s PHP version?
In WordPress, go to Tools → Site Health → Info → Server. You can also check your hosting control panel or ask your host.
Was my website hacked?
Not necessarily. Being vulnerable doesn’t mean you were breached. But exploitation attempts have been reported, so you should patch now and check for warning signs such as unknown admin users or unexpected files.
Do Shopify, Wix or Squarespace sites need updating?
No action is needed from you on these platforms, as the provider manages the servers.
Sources
- CERT-EU Security Advisory 2026-018: Critical Vulnerabilities in PHP
- ABC News: Australian government sites among those exposed to ‘critical’ PHP software flaw
- Information Age: Govt sites go down after AI finds critical PHP vulnerabilities
- Reuters via US News: What is PHP and why did it take government websites offline?
- CNBC: Government websites in Europe and elsewhere go dark as software flaw sparks security scramble
- RTÉ: Websites go dark as AI exposes critical security flaws
- Qualys: Two critical PHP flaws could hand attackers your web servers
- Huntress: Rapid response on PHP2Shell
- W3Techs: Usage statistics of PHP for websites
// keep diving


