Two critical security vulnerabilities in PHP, collectively known as PHP2Shell, prompted urgent security updates across the web hosting industry in October 2026. Because PHP powers WordPress and many other websites, the announcement was significant for both website owners and hosting providers.
The good news for customers using 20i-hosted services is that 20i reported completing the security patch rollout across its PHP platforms on 21 October 2026, including fixes backported to older PHP releases. Here is what happened, what was fixed and why timely server maintenance matters.
What happened?
On 21 October 2026, the PHP project published emergency fixes for two vulnerabilities known as CVE-2026-109618 and CVE-2026-109619. Together they became known as PHP2Shell.
Both flaws affect the PHP programming language itself, rather than a particular WordPress theme or plugin. They involve problems with the way PHP handles memory when processing web requests. Under certain conditions, an unauthorised attacker could potentially execute code on a vulnerable server or access sensitive information held in memory.
The vulnerabilities were rated critical, with a CVSS v4.0 score of 9.2. They have also been added to the US Cybersecurity and Infrastructure Security Agency's catalogue of known exploited vulnerabilities.
This is why the issue required urgent action: a website could have an up-to-date WordPress installation and still be exposed if the underlying PHP runtime had not been patched.
Which PHP versions were affected?
The PHP project released fixes for the supported branches on 21 October 2026:
| PHP branch | First fixed version |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
PHP 8.1 and earlier are no longer supported by the PHP project. Where hosting providers supply their own backported security patches, an older version number may not tell the whole story. Nevertheless, moving to a supported PHP branch remains the best long-term approach.
How did 20i respond?
20i published updates through its hosting status communications as it responded to PHP2Shell on 21 October 2026.
- Initial protection: Additional security measures were introduced while the PHP fixes were prepared and deployed.
- Updated PHP releases: 20i made the patched PHP versions available, including 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
- Older PHP branches: The hosting provider also reported deploying backported fixes for older PHP versions offered on its infrastructure.
- Platform-wide completion: By approximately 20:01 UTC (9:01pm BST) on 21 October, 20i's status reporting stated that PHP versions across its platforms were fully patched, including Cloud Servers.
This response is a useful example of why the hosting provider matters. Security fixes for PHP must be installed at server level; simply updating WordPress or activating a security plugin is not enough to address a PHP runtime vulnerability.
For further details, see 20i's PHP2Shell guidance and its platform status updates.
Was my WordPress website affected?
If your website was running a vulnerable PHP build before the update, it may have been exposed to the issue. That does not mean that the website was compromised.
20i's announcement describes the provider's patch deployment, not an individual forensic investigation of every customer's website. If you have concerns about suspicious activity during the exposure period, ask your website administrator or hosting provider to review relevant logs and investigate any indicators of compromise.
Customers using other hosting providers should check their provider's own PHP2Shell statement or confirm that the appropriate security patch has been installed.
Do website owners need to do anything?
For a site on 20i's managed hosting platform, 20i's reported platform-wide patch deployment should have addressed the underlying vulnerability without needing customers to manually patch the server. However, there are still some sensible checks to make:
- Confirm your hosting arrangements. Shared hosting, managed servers and self-managed VPS configurations can have different responsibilities. If you maintain your own PHP installation, verify its patches and restart the relevant PHP services.
- Use a supported PHP version. A backported security fix protects against the specific reported vulnerabilities, but remaining on an end-of-life PHP branch carries other compatibility and security risks.
- Keep WordPress updated. WordPress core, themes and plugins still require their own maintenance, even though their updates are not the PHP2Shell fix.
- Maintain reliable backups. Regular, restorable backups remain an essential part of website security and business continuity.
- Investigate unusual behaviour. Unexpected files, administrator accounts, error spikes or other suspicious activity deserve attention.
Why this matters beyond PHP2Shell
One of the biggest lessons is that website security is not just about installing WordPress updates. The underlying server software needs attention too.
A well-maintained website combines a supported PHP runtime, timely hosting security patches, updated software, appropriate access controls, monitoring and reliable backups. These layers work together to reduce risk.
PHP2Shell also demonstrates the difference between a temporary mitigation and a security fix. Firewall rules can help reduce exposure while a patch is being deployed, but updating the vulnerable PHP software addresses the underlying cause.
Summary
PHP2Shell involved two critical vulnerabilities in the PHP runtime disclosed in October 2026. Security releases were published on 21 October, and hosting providers needed to apply them promptly.
20i reported completing its PHP2Shell patch rollout across its hosting platforms on the same day, including backported fixes for older versions. This was a server-level fix, not a WordPress plugin update.
If you manage a WordPress website, the wider lesson is clear: choose hosting that takes security updates seriously, keep PHP and WordPress maintained, and ensure you have a reliable backup and recovery process.
Further reading: 20i: PHP2Shell security updates · NHS England: Critical vulnerabilities in PHP · 20i hosting status.







