PHP Fixes Are Out, but Unpatched Websites Still Pose the Main Risk

PHP Fixes Are Out, but Unpatched Websites Still Pose the Main Risk

N
News Editor
2026-10-22 22:21:46
PHP has released fixes for the two critical flaws known as PHP2Shell, but the patch only works once website operators install it and restart affected services. That leaves a gap between disclosure and real protection, especially for older servers that no longer receive official releases. According to PHP release notes, the patched versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35, and the project said plainly that updating is the only safe option. Attack activity has already surged. Cloudflare CEO Matthew Prince said the company saw thousands of exploit attempts in the 10 hours before public disclosure, tens of thousands within 45 minutes after, hundreds of thousands within two hours, and millions since. Amazon said one of its decoy servers recorded an attempt on October 17, four days before the bugs became public, and its CISO CJ Moses wrote that PHP2Shell is now being broadly exploited in the wild. For everyday users, the immediate risk sits mostly with the websites they visit rather than their own devices. No confirmed data breach has yet been tied to PHP2Shell, and no crypto exchange has publicly reported a related breach. Still, hacked web servers can serve fake pages, a particular concern for crypto users asked to connect wallets and approve transactions.

One day after two PHP flaws pushed governments and major organizations to take websites offline, fixes are now available. That does not mean every site is safe again. For most people, the immediate risk sits with the websites they visit, not with their phones or laptops.

The two bugs, nicknamed PHP2Shell, can let an outside attacker take control of a vulnerable server without logging in. PHP remains a major part of the web stack, running behind roughly 70% of websites whose server-side language is known.

The patch is out, but deployment is the real issue

According to PHP release notes, the project shipped versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 on Wednesday. PHP said, 「There are no complete mitigations, updating is the only safe choice.」 As of Thursday, no follow-up patch had been issued.

The catch is simple: PHP does not update itself. Hosting providers, internal IT teams, and individual site owners all have to install the fix on their own servers and restart the software before the patch takes effect.

So while a fix exists, the sites people visit may still be exposed if administrators have not yet applied it.

Older versions are a weaker point. PHP 8.1 and earlier no longer receive official releases. PHP's security team did post minimal patches for 7.4, 8.0, and 8.1 for users who compile the software themselves, but those versions are no longer in the normal release stream.

Exploit attempts have surged, while confirmed break-ins remain unclear

Attackers moved quickly. Cloudflare CEO Matthew Prince said the company saw thousands of exploit attempts across its network in the 10 hours before public disclosure, tens of thousands in the 45 minutes after the announcement, hundreds of thousands within two hours, and millions since.

Amazon pointed to even earlier activity. The company said one of its decoy servers logged an attempt on October 17, four days before the bugs became public. Amazon CISO CJ Moses wrote, 「It remains unclear how the actor acquired exploit information prior to disclosure,」 and added that PHP2Shell is 「now being broadly exploited in the wild.」

Government agencies, though, have not reported confirmed successful intrusions so far. Thomas Caspers, vice president of Germany's federal cybersecurity agency BSI, said the agency had seen attacks but no successful use of the flaws. He added, 「It seems a little bit more complicated than expected to exploit.」 Japan's Chief Cabinet Secretary, Minoru Kihara, also said no attacks exploiting the flaws had been confirmed.

Those statements are not contradictory. An exploit attempt is not the same as a confirmed breach, and successful intrusions are often discovered later rather than in real time.

PHP Foundation says the warning signs existed, but the response lagged

In a blog post published Wednesday, the PHP Foundation said its 2024 security work had already 「found the first signs of the OOM problem behind CVE-2026-109618,」 referring to the out-of-memory issue at the center of one of the two flaws.

The foundation said the team developed 「several competing approaches」 to fix the issue but 「struggled to choose between these and feared the repercussions of shipping the wrong choice.」 It also said, 「Without the Foundation's funding it would have been impossible to have multiple people work on this issue full time.」

The foundation was direct about the delay. 「We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources,」 it wrote. It also said the security team, which previously required consensus, will now decide by majority.

For software that supports a large share of the web, the foundation said security work still depends on a small group of foundation-funded developers and limited volunteer help.

Why some websites are still offline

Patching takes time, and taking systems offline was part of the official guidance for organizations that could not patch immediately. The UK's National Cyber Security Centre told organizations to consider 「taking the system offline until it can be fully mitigated.」

According to TechRadar, the list of affected services on Wednesday included Wikimedia services, Orange websites and apps across dozens of countries, 32 UK government services, Dutch hospitals, and Germany's federal IT provider ITZBund.

By Thursday, the UK's Office for Budget Responsibility and Edinburgh's council website were back online. Others remained down. DutchNews reported that the Dutch anonymous crime-reporting site Meld Misdaad Anoniem was still offline on Thursday morning.

Should users change passwords now?

Not because of PHP2Shell alone, at least not yet. No confirmed data breach has been tied to the flaws so far, and changing every password immediately will not solve the problem if a site's server is still unpatched.

The practical steps remain familiar: use unique passwords for each account, turn on two-factor authentication, and watch for breach notifications from companies in the coming weeks. If one arrives, change that password and any other account where it was reused.

Website operators face a broader checklist. Tag1 said patching closes the door but does not show whether someone got in earlier. The firm advised checking for PHP files that were not uploaded by the site owner, new scheduled tasks, and new accounts, and rotating database passwords and API keys on any internet-facing server that ran a vulnerable version.

What this means for crypto users

Binance founder Changpeng Zhao offered a short warning on X: 「Call me paranoid, but be extra careful visiting ANY web site in the next few days.」

He referred to the two reported PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which affect servers running the web programming language.

For crypto users, a compromised web server can present a fake version of a legitimate site. The blockchain itself may be unaffected, but the front end can still become the attack surface, especially if users are prompted to connect wallets and approve transactions that drain funds.

For the next few days, the article advises users to double-check what they sign, rely on bookmarks instead of clicking links, and use a hardware wallet if they have one. So far, no crypto exchange has publicly reported a breach tied to PHP2Shell.

The broader risk has not passed

Browsing the web today is not fundamentally different from last week: it is not perfectly safe, and the main exposure sits on servers that have not been patched. Security company Mallory counted roughly 884,000 internet-facing hosts running PHP versions that receive no official fix.

Amazon's message to defenders was that the incident should not be treated as finished. 「Defenders should not assume the public disclosure date is the earliest date of exploitation.」

That means any server that ran a vulnerable version since at least October 17 should be investigated, not merely patched, to determine whether it was compromised before the fix was applied.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
10200

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.

PHP Fixes Are Out, but Unpatched Websites Still Pose the Main Risk | Bit.Fan