A series of global PHP cyberattacks prompted urgent security action from website hosting providers, businesses and government organisations in October 2026, following the discovery of critical vulnerabilities in one of the internet’s most widely used programming languages.
The incident made international headlines as cybersecurity specialists reported attempts to exploit the weaknesses, while some organisations temporarily took websites and online services offline to protect their systems.
In the UK, BBC News reported disruption to 32 government services, with a further four partially unavailable.
To understand more about business technology , head to our ‘Explained In Simple Terms services, helping organisations understand modern digital tools without technical jargon.
Article Table of Contents and Quick Links
How the PHP Cyberattack Developed
- 17th October 2026: Amazon Threat Intelligence detected an early attempt to exploit the PHP vulnerabilities.
- 20th October 2026: Information about the vulnerabilities began circulating publicly.
- 21st October 2026: Further exploitation attempts were reported, and emergency PHP security updates were released.
- 22nd October 2026: International news coverage highlighted widespread security concerns and disruption to government services.
- 31st October 2026: This article is published
The dates reflect reported activity and disclosures, rather than a definitive record of every attack.
But what caused the security concerns, how were websites affected and what was done to protect them?
What Is PHP and What Triggered the Global PHP Cyberattacks?
On 21 October 2026, the PHP development team released security updates addressing two critical vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619.
PHP is a programming language used behind the scenes by millions of websites, including those built with WordPress. It helps websites process information, communicate with databases and deliver interactive features.
The vulnerabilities involved weaknesses in how PHP handled certain operations. Under vulnerable conditions, attackers could potentially exploit these weaknesses to execute unauthorised code on a server.
Both vulnerabilities received a critical severity rating of 9.2 out of 10, highlighting the potential seriousness of a successful attack.
Why Was the PHP Security Vulnerability So Significant?
The scale of the concern was partly due to the widespread use of PHP.
The Guardian reported that approximately 70% of websites use PHP. To be clear, this figure describes the prevalence of the technology, not the proportion of websites successfully attacked.
Nevertheless, it illustrates why a serious vulnerability in widely used software can quickly become an international concern.
Businesses, public services, educational institutions and government departments may all operate websites that depend on PHP.
Depending on the server configuration and software version, a successful exploit could potentially expose sensitive information, disrupt online services or allow attackers to interfere with affected systems.
Were Millions of Websites Hacked?
Reports described millions of attempts to exploit the PHP vulnerabilities, but an attempted cyberattack is not the same as a successful breach.
Cybercriminals frequently use automated tools to search the internet for systems running vulnerable software. These tools can generate large numbers of requests as attackers attempt to identify weaknesses.
The reported volume of attempted exploitation therefore does not establish that millions of websites were successfully compromised.
During the initial response, authorities and cybersecurity specialists emphasised the importance of applying security updates and investigating any evidence of unauthorised activity.
Was This a DDoS Attack?
Some of the disruption was discussed alongside concerns about Distributed Denial of Service, or DDoS, attacks.
A DDoS attack occurs when a website or server is overwhelmed with large volumes of traffic, making it difficult or impossible for legitimate visitors to access the service.
However, the central PHP security incident involved attempts to exploit software vulnerabilities.
The two types of cyberattack are different. A DDoS attack primarily targets the availability of a service, whereas exploitation of a software vulnerability may allow an attacker to access or interfere with systems in ways they should not be able to.
A website becoming temporarily unavailable does not, by itself, establish that it has suffered a DDoS attack or a successful security breach.
Why Were Government Websites and Other Services Taken Offline?
One of the most visible consequences was the temporary disruption of online public services.
BBC News reported that 32 UK government services were unavailable, with another four partially unavailable during the incident.
In some cases, organisations deliberately restricted access while technical teams assessed the risks and applied security measures.
Taking a website offline can be a precautionary decision. It may reduce the opportunity for attackers to exploit a vulnerability while the underlying software is being secured.
It is therefore important not to assume that every unavailable website had been hacked.
How Were the PHP Vulnerabilities Fixed?
The PHP development team released security updates on 21st October to address the identified vulnerabilities.
The fixes were included in updated PHP releases, including:
- PHP 8.2.35
- PHP 8.3.36
- PHP 8.4.27
- PHP 8.5.12
Hosting providers and technical teams then needed to assess their systems and deploy the appropriate fixes.
Some hosting companies introduced additional protective measures while updates were being prepared or applied. These could include tighter traffic filtering, firewall protections and temporary restrictions on affected services.
However, protective measures do not necessarily replace the need to correct the underlying software vulnerability.
Applying the relevant PHP security update was the essential long-term response.
What Should Website Owners Check?
For businesses with a website, the incident highlights the importance of knowing who is responsible for maintaining the software running behind their website.
Website owners should establish whether their hosting provider has applied the necessary PHP security fixes and whether the website is running a supported software version.
They should also ensure that their content management system, themes and plugins are being maintained appropriately.
Where updates are managed by a hosting provider or website maintenance company, it is reasonable to request confirmation that the necessary checks and security measures have been completed.
Older or unsupported software may require additional work to bring it onto a maintained version.
Read our Website Software Updates Explained In Simple Terms article to better understand what they are, why they are needed and how to prepare for them.
What Can Businesses Learn From the Global PHP Cyberattacks?
The October 2026 incident demonstrated how quickly a vulnerability in widely used technology can become an international cybersecurity concern.
It also showed the importance of cooperation between software developers, security researchers, hosting providers and organisations responsible for operating websites.
No website platform can be guaranteed to remain free from vulnerabilities. New weaknesses can be discovered even in established software that is used by millions of organisations. The key is how those weaknesses are identified, communicated and addressed.
Keeping software supported and updated, maintaining appropriate security measures and responding promptly to emerging threats all help reduce the risk of disruption or compromise. Security should be considered throughout the website development process, from choosing the hosting environment and software through to ongoing maintenance and monitoring.
For businesses that rely on their websites for enquiries, customer information or online services, the incident is a reminder that website security requires ongoing attention, even when everything appears to be working normally.

