
Critical PHP Vulnerabilities (php2shell): How We Protect You
Summary
On 21 October 2026, the PHP security team released an emergency update fixing two critical vulnerabilities, known as CVE-2026-109618 and CVE-2026-109619 (nicknamed “php2shell”).
All Hixon Group Managed WordPress hosting platforms have been updated to the patched versions. You do not need to take any action.
What is PHP and why does it matter?
PHP is the software on the web server that runs WordPress, its themes and its plugins. Every time someone visits your website, PHP builds the page they see. Because it sits underneath everything, a weakness in PHP can put a website at risk even when WordPress and every plugin are fully up to date. Keeping PHP patched is a core part of our managed hosting.
What are the vulnerabilities?
Both are rated 9.2 out of 10 (Critical) and can allow unauthenticated remote code execution. In plain terms, an attacker could run their own code on a web server without logging in.
- CVE-2026-109618 (out-of-memory corruption): When PHP runs out of memory while handling a specially crafted request, it can be left with half-prepared internal data, which it then mistakenly treats as valid. An attacker can abuse this to take control.
- CVE-2026-109619 (stale data between requests): Internal data from one visitor’s request could survive after it should have been cleared, and be reused by the next request handled by the same server process. Again, this can be abused to run malicious code.
They affect every supported version of PHP (8.2 to 8.5) and older unsupported versions, and every common way of running PHP on a web server. The fixed versions are PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
What made this one especially serious is that the attack can happen before WordPress itself loads, so security plugins and firewalls inside WordPress cannot stop it. Details also leaked ahead of the official release, so attackers had a head start.
What would happen if this wasn’t fixed?
On an unpatched server, an attacker could potentially:
- Take full control of the website, adding malware, spam pages or redirects to scam sites
- Steal data, including customer details, form submissions, order information and passwords stored in the site’s database
- Install hidden backdoors that let them come back later, even after the original hole is closed
- Use the server to attack others, sending spam or attacking other websites, which can get your domain blacklisted
- Take the site offline entirely
For a business, this could also mean a reportable personal data breach under UK GDPR, along with the cost, disruption and reputational damage of recovering. Critical vulnerabilities like these are often exploited within hours of becoming public, which is why speed matters.
Response Timeline
- 20 October: The PHP security team gave advance warning of the release. We reviewed our platforms and applied the recommended protective settings, such as disabling session upload progress tracking and tightening request size limits, to reduce exposure before the fix was available.
- 21 October, 14:00: The fixes were released.
- 21 October, 16:00: All Managed WordPress hosting platforms were updated to the patched PHP versions, and every server was checked to confirm the update had applied and websites were working normally.
We have found no evidence of these vulnerabilities being exploited on our platforms.
How we handle security updates
Our process for any security release, whether it’s PHP, the server operating system or WordPress:
- Monitor: We track official security advisories from PHP, our server software vendors and the WordPress project, including advance warnings.
- Protect early: Where a vendor publishes interim protective measures, we apply them while waiting for the full fix.
- Assess: As soon as a fix is released, we review its impact and prioritise by severity. Critical issues like this one go to the front of the queue.
- Deploy: Critical fixes are applied as soon as possible after release, usually with no downtime for you.
- Verify: We confirm every server is patched and every site is running normally.
Ongoing monitoring
Patching is only one layer. Our platforms are continuously monitored for unusual activity, including suspicious requests, unexpected traffic spikes, unauthorised file changes and service failures. If something looks wrong, our team investigates straight away.
Do I need to do anything?
No. PHP updates are handled entirely by us as part of your Managed WordPress hosting. As good practice, we’d still recommend:
- Using strong, unique passwords and two-factor authentication on WordPress admin accounts
- Removing plugins and themes you no longer use
- Letting us know if you notice anything unusual on your site