A major flaw found in the PHP coding
language that powers an untold number of websites across the internet has seen
scores of sites taken offline as they attempt to patch out the severe
vulnerability.
If you've found your favorite
website has been unavailable over the last few days, there's a chance it's
related to this security incident.
Here, I have put together a list of
as many affected websites as we can find, along with reasoning given by the
sites where possible.
India
The India-specific exposure figure
makes the issue more than a routine software update. The report identifies over
50,000 facing assets running PHP in the country, with 159 belonging to
government entities. These figures indicate the scale of the digital footprint
that may need to be examined. These are potential exposure figures, not
confirmed hacks. For security reasons, I cannot disclose the names of the
affected websites, as they are currently undergoing security patching.
CERT-In, India's cyber security
agency, issued a warning advising organizations to update vulnerable PHP
installations.
Global sites (USA based)
- Wikimedia / Wikipedia
The Wikimedia Foundation said it had taken some services offline to patch the PHP security vulnerability.
The group runs popular websites like Wikipedia and said in a blog post that "You may see outages for our wikis as we work on this, and we have deliberately taken many of our supporting services offline until they can be safely patched." - Internet Archive
The Internet Archive, which backs up pages across the internet, was offline on October 21. The organization posted on X to say that "Archive.org is currently offline. We are working to restore service now," although this was not definitively linked to the PHP incident. - Orange Telecom
The telecommunications giant Orange has announced thats it's "temporarily" suspended access to several of its websites and apps that use PHP.
That move affects dozens of countries, mostly in Europe but also Africa and the Middle East. Orange called it a "precautionary" measure and that each country would communicate which sites have been affected locally.
UK sites
A UK minister has revealed that 32
government services are currently offline due to the PHP security threat, while
a spokesperson added: "Our work has begun with OpenAI and NCSC to fix
vulnerabilities in government systems".
Europe
- Belgium: The Foreign Ministry
- Czechia: The national government website
- Denmark: Municipal IT company Kombit
- Finland: Public government service websites
- France: Local government (prefecture) websites run by
the Interior Ministry
- Germany: The federal IT service provider ITZBund
- Netherlands: The National Cyber Security Centre
- Netherlands: The Port of Rotterdam
- Netherlands: Government website Overheid.nl
- Netherlands: National football association KNVB
- Netherlands: The websites of the five largest political
parties
- Netherlands: The websites of many national hospitals.
Technical overview: what php2shell
actually breaks?
Unauthenticated RCE on the PHP web
runtime
The latest critical PHP
vulnerabilities, collectively tracked as php2shell, allow unauthenticated
remote code execution (RCE) and memory corruption across web servers running
PHP. "Unauthenticated" means the attacker does not need a valid application
session, WordPress cookie or admin password for the serious cases described by
the PHP security team and major cloud vendors.
Affected web-serving installations
include common SAPIs and stacks such as:
- Apache with mod_php (called out as highest risk in
PHP's guidance)
- PHP-FPM behind Nginx or Apache
- php-cgi
- FrankenPHP
- LiteSpeed PHP handlers
On the highest-risk paths, a mal
Which PHP versions are safe?
As of the 21 October 2026 emergency
release, move to one of these fixed versions (or newer on the same line):
- PHP 8.5.12
- PHP 8.4.27
- PHP 8.3.36
- PHP 8.2.35
How to check your website in 2
minutes
- Log in to WordPress admin.
- Go to Tools → Site Health → Info → Server.
- Find PHP version (and note the SAPI if shown: fpm-fcgi,
apache2handler, and so on).
- Compare it with the safe list above.
How to fix it (step by step)
Option A: You use shared or managed
WordPress hosting
- Open a support ticket today.
- Ask: "Are we on PHP 8.2.35, 8.3.36, 8.4.27 or
8.5.12 (or your patched package for php2shell / CVE-2026-109618 and
CVE-2026-109619)?"
- Ask them to confirm the version after restart.
- If they mention only a firewall (WAF), thank them then
still insist on the PHP upgrade. A firewall is temporary cover, not the
full fix.
- When they reply, re-check Site Health yourself.
Option B: You or your developer
manage a VPS / cloud server
- Upgrade PHP packages to a fixed release from your OS
vendor or trusted PHP packages.
- Restart PHP-FPM / Apache / LiteSpeed workers so old
processes die.
- Verify the live web PHP version (not only php -v on
CLI).
- Smoke-test the homepage, login, forms and checkout.
- If you use Docker or Kubernetes, rebuild and redeploy
images do not assume old containers updated themselves.
Option C: You cannot patch
immediately
- Prioritise any site open to the public internet.
- Keep host/WAF protections on.
- If you are stuck on very old PHP and cannot upgrade
today, seriously consider taking that site offline until it is fixed that
is the advice several cyber agencies are repeating.
- Technical teams may also apply vendor-documented compensating controls (WAF body limits, disabling risky ini features, more aggressive worker recycling). Treat every one of those as partial. Patch remains mandatory.




