·
Patching and Software
·
5 min read
The Back Door You Didn't Know You Had
In the first 24 hours of PHP2Shell, Australia was the third most-targeted country in the world. Whether that meant a routine update or a week offline was decided years earlier.

If your firm has a client portal, an online booking system, a document upload page, or a custom job-tracking tool built years ago that still “just works,” there is a high chance it runs on PHP. Most business owners have never heard of PHP, yet it sits behind the majority of these everyday web tools.
In October, two critical flaws in PHP, nicknamed PHP2Shell, turned those quiet systems into open back doors. This article covers how a problem known for two years became a 12-hour emergency, why the usual patching advice is under strain, and how to make sure your next emergency is a routine update.
BOTTOM LINE UP FRONT
Two critical flaws in PHP, first spotted in 2024, were fixed in a rush on 21 October after the details leaked. Attack attempts reached the millions within about 12 hours, Australia was the third most-targeted country, and working attacks were confirmed within three days. Businesses on supported software applied an update and moved on. Those on unsupported versions had nothing to apply. The fix is to know what you run, keep it on supported versions, and treat a critical alert as a same-day job.
Known for two years, fixed in a week
PHP is the programming language running on the server behind roughly three in four websites, and behind many business tools that happen to have a web page. In 2024, an outside security audit of PHP flagged a weakness. The PHP Foundation now says the fix "stalled and restarted repeatedly over months". In August 2026, two research teams, both using AI tools, found it again and showed it could be used to take over a web server without a password. The flaws, now called PHP2Shell, were rated 9.2 out of 10.
The secret got out
The fix was planned as a quiet, coordinated release. Instead, the secret got out three ways in one day. Amazon's decoy servers had already recorded an attempt on 17 October, four days early, and Amazon says it's unclear how that attacker knew. In the early hours of 21 October, the flaws' ID numbers appeared online. One of the research firms posted a demonstration video, then pulled it. Then Chainguard, a software packaging company, published fixed versions six hours ahead of the agreed time. The PHP Foundation says that broke the embargo; Chainguard's founder says he "made the call to get these out early when exploits hit in the wild". Either way, anyone comparing old code with new could now see where the hole was. The release was brought forward.
Fixed at midnight, attacked by breakfast
The official fix landed at midnight on Wednesday night, 21 October, Queensland time. Cloudflare's CEO reported thousands of attempts in the ten hours before, tens of thousands in the first 45 minutes after, hundreds of thousands within two hours, and millions by late morning.
In the first 24 hours, Australia was the third most-targeted country in the world, behind only the United States and Indonesia. "Business" was the most targeted sector.
Most early traffic was scanning, and Germany's cyber agency said the flaws were "a little bit more complicated than expected to exploit". That held for three days. On 24 October, a researcher's decoy servers recorded 35 working remote shells. On 26 October, the US cyber agency listed PHP2Shell as known to be exploited. The next day, a European sensor network logged its busiest hour yet.
The 48-hour rule meets a 12-hour reality
ASD's Essential Eight says internet-facing systems must be patched within 48 hours when a flaw is critical or a working exploit exists. The US agency gave its own departments three days. Attackers needed about twelve hours. The researchers who found the flaws say AI tools let them build working attacks against several different applications in hours. Assume attackers have the same tools. The 48-hour clock hasn't changed. What's changed is how much of it attackers use up before you've read the alert.
PHP isn't just your website
WordPress runs on PHP, and WordPress is 57% of Australian business sites with an identifiable platform. But PHP also sits under client portals and booking forms, file-sharing servers (Nextcloud), CRM and invoicing tools (SuiteCRM, Invoice Ninja), help-desk and asset registers (GLPI, Snipe-IT) and staff training sites (Moodle). In a factory, it's often behind the network monitoring dashboard (Zabbix, LibreNMS), the phone system's admin page (FreePBX) and the office storage box's web interface. Researchers have shown working attacks against Laravel, Symfony, MediaWiki and phpBB, not only WordPress. Anything reachable from the internet comes first. Internal tools are the next door along.
What you can do: For every tool with a web page, ask the vendor or developer two questions: does it run PHP, and is the October fix installed?
Almost half had no update to apply
TheColab.ai checked 1.4 million .com.au sites on 22–23 October. Of the 192,892 that revealed their PHP version, 46% were on a version the PHP project no longer supports. Two practices, same night. Practice A, on a supported version: the host applied the update, the owner confirmed it, done. Practice B, on an old version: there's no official update. The responsible path is offline, upgrade, test, validate, back online, and sometimes that means a rebuild. Same flaw, very different week, decided years earlier. By 24 October, two in three tracked sites still looked open. And PHP 8.2, supported today, stops getting security fixes on 31 December 2026.
What you can do: If anything runs PHP 8.1 or older, start the upgrade now. If it runs 8.2, book the upgrade before 31 December.

What this means for your business
ASD's ACSC rated this alert critical, advised organisations to identify PHP in their environments and apply updates, and took its own website offline while it did the same. Under the Privacy Act, a breach of client files likely to cause serious harm must be reported to the OAIC and the people affected. A client portal on unsupported software is hard to defend to either.
Our view, not established fact
We expect AI-assisted research to keep finding serious flaws in widely used software, and the gap between a fix and mass attack attempts to keep shrinking. A third PHP flaw was disclosed on 23 October; we expect it's never just one patch. We expect the businesses that cope best will know what they run, keep it supported, and treat a critical alert as a same-day job.
What you should do next
List every website, portal and tool your business runs that has a web page.
Name who maintains each one and confirm its PHP version.
Get anything on PHP 8.1 or older upgraded, and book PHP 8.2 for before 31 December.
Agree who acts on a critical alert, and how fast, before the next one.
Get an independent view of whether these arrangements actually work.
Hardrock Cyber provides independent assessments and readiness work for Australian businesses, including the Essential Eight. We never connect to your network or change your systems, settings or day-to-day operations. Request a Confidential Enquiry.
P.S. One observation from the dark web side. On 22 October, Alexander Wilczek, dark web researcher and founder of Rivanorth, noted: "The silver lining of PHP2Shell is that many dark web forums were down for maintenance. Sadly, they seem to have recovered and back up online faster than legitimate websites." If criminal forums can get their PHP fixed and back online first, so can your business.
Sources: PHP Foundation (via TechTarget) · php.net · ASD's ACSC · ASD Essential Eight · Amazon Threat Intelligence · Socket (Chainguard) · Cloudflare (via The Next Web) · Imperva · The Next Web (BSI) · Wiz · Tenable · SecurityWeek · CISA (via BleepingComputer) · Delft Threat Intelligence Lab · TheColab.ai · Cyber Daily · OAIC · Rivanorth. Figures as at 28 October 2026.
Frequently asked questions
What is PHP2Shell?
How do I know if my business uses PHP?
My systems are on an older PHP version. What are my options?
Were Australian businesses hacked?
Why does PHP 8.2 matter?
Not sure where your business stands?
Independent assessments, Australia-wide. Every enquiry is confidential.
Request a Confidential Enquiry
More Insights
Practical reading on the cyber risks facing Australian businesses, and what to do about them.
Get started
Turn reading into action.
A confidential, no-obligation conversation about what this means for your business.


