Authored by: Bryan Lachapelle, President & CEO
Authored by: Ashley Barron, Sales & Marketing Manager
Earlier this week we shared what was going on with PHP2Shell, the pair of critical PHP flaws that sent businesses and governments around the world scrambling to take websites offline. We said we'd follow up as things developed, so here's where it all stands today.
The short version: attackers are actively trying to use these flaws, but researchers now think a large-scale wave of attacks is less likely than they first feared. Either way, the advice hasn't changed. If a website or tool you rely on runs on PHP, it needs the update. PHP has also flagged a third, much less likely issue, which we cover further down.
Several security companies have now confirmed people are trying to take advantage of these flaws. Cloudflare reported early attack attempts on the morning of October 21, a few hours before PHP even released its fix. Security firm watchTowr also reported attempts against both flaws later that day, and Amazon's threat intelligence team said it saw attempts starting as early as October 17, before the details were made public.
An attack attempt isn't the same as a successful break-in, though. Here in Canada, the Canadian Centre for Cyber Security (the federal government's lead agency on cyber threats, often called the Cyber Centre) issued an alert on October 21. At the time, it said it hadn't seen any active attacks yet, but warned that could change quickly. It's urging Canadian organizations to find any systems running PHP, starting with anything that faces the internet, and apply the updates right away. For anything that can't be fixed right away, it recommends taking it offline temporarily. That's why some Government of Canada websites went dark this week as a precaution.
Not every researcher sees this the same way. Security firm Sansec, which focuses on online stores, said on October 22 that widespread attacks now look less likely than they expected on release day. Their reasoning is that a successful attack needs specific knowledge about the target server, and the exploits floating around online don't work against a standard PHP setup.
That's encouraging, but other firms are still seeing attack activity, so it isn't a reason to wait.
PHP has clarified that one setup carries the highest risk. It's called mod_php, which is a common way of running PHP on Apache web servers. In plain terms, it's one of several ways PHP can be "plugged into" the software that delivers a website. PHP says researchers have shown an attack working on this setup before the website's own code even runs. Other setups are still at risk too, and your web host or developer will know which one your site uses.
If your site runs PHP 8.1 or older, there's a little more help available now. Some companies that specialize in supporting older software, like TuxCare, are rolling out fixed versions for PHP releases the PHP project no longer updates. That can buy time, but it's a stopgap rather than a long-term plan.
It's also worth knowing that PHP 8.2 only receives security fixes until December 31, 2026. So even if your site is on 8.2 and gets patched this week, it's a good time to start planning the move to a newer version.
PHP has expanded its list of temporary settings changes for teams that can't update right away. These include tightening memory and upload size limits and turning off a feature that tracks file upload progress. They can reduce the risk from certain types of attacks, but PHP is clear that none of them make a website safe, and some can affect how a site works, like blocking larger file uploads. These are changes for your web host or developer to weigh, not something to try on your own. Updating is still the only complete fix.
On October 23, PHP shared a heads-up about a third, separate issue. This one is much less of a worry. It only affects websites set up in a very unusual way, so PHP will fix it in its next regular update rather than rushing out an emergency patch. That also means this week's updates don't cover it yet. In the meantime, PHP suggests turning off the upload progress feature mentioned above, which fully protects against this issue. If your web developer already turned it off this week, they can leave it that way and there's nothing more to do.
We've been flagging this issue to our clients since it broke, and for clients who've asked, we're reaching out to their web developers on their behalf to ask the right questions. If you'd like us to do the same for you, just let us know.
If you haven't heard from your web host, developer or software vendors yet, here's what we'd ask:
- Does our website, or any software we use, run on PHP?
- Has the PHP update itself been applied (not just WordPress or plugin updates), and has the site been tested since?
- Have you turned off the upload progress feature PHP recommended on October 23?
- Which PHP version are we on, and is it still supported?
- If we're on PHP 8.2 or older, what's the plan for upgrading?
- Is there any downtime we should plan around?
As before, be careful with any unexpected email about this issue that asks you to log in or "fix" something.
We'll keep watching this one and share anything that changes what you should do. If you have any questions, just reach out to our team at 905-228-4809 (Niagara) or 705-885-0993 (Barrie).
Sources:
- Canadian Centre for Cyber Security: Alert AL26-026, Critical vulnerabilities impacting PHP (October 21, 2026)
- Canadian Centre for Cyber Security: Statement regarding critical vulnerabilities in PHP (October 21, 2026)
- Global News: Ottawa taking down some federal websites over critical global vulnerability
- PHP: Security advisory and release announcements (October 21, 2026)
- PHP: Informational advisory, session upload progress (October 23, 2026)
- Sansec: PHP2Shell research update (October 22, 2026)
- The Hacker News: PHP issues emergency patches for PHP2Shell
- Tenable: php2shell FAQ
- SOCRadar: PHP2Shell affected versions and fix
- TuxCare: Patches for end-of-life PHP versions
