On 21 October 2026, the PHP project released emergency fixes for two critical security vulnerabilities, publicly tracked as CVE-2026-109618 and CVE-2026-109619 and already being referred to in the security community as “php2shell”. Both allow unauthenticated remote code execution — meaning an attacker could potentially run arbitrary code on a vulnerable server without needing a login, a plugin bug, or any user interaction at all. We want to explain what happened, why it mattered so much, and confirm that every server across our hosting platform has already been updated to the patched versions.
PHP’s security team gave advance notice on 20 October that a critical release was coming, rating both issues CVSS v4.0 9.2 — close to the maximum possible severity score. The release followed the next day with fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
The two flaws were both memory-handling bugs inside PHP’s core request lifecycle, rather than anything to do with a specific plugin, theme or application. One (CVE-2026-109618) could let PHP treat partially-initialised request data as valid after an out-of-memory event interrupted normal processing. The other (CVE-2026-109619) involved request-owned internal state surviving after its memory had technically been freed, meaning a later, unrelated request handled by the same worker process could end up using stale data before it should have. In the wrong circumstances, either could be manipulated into executing attacker-supplied code.
Read the BBC article here:
https://www.bbc.co.uk/news/articles/cmly0lg3w5x2o
Read the PHP advisory here:
https://www.php.net/index.php#2026-10-21-5
Most PHP security releases are routine — most businesses never notice them. This one was different for a few reasons. First, it required no authentication at all: the vulnerable code could be reached by anyone able to send a request to the server, before any application-level security (login forms, firewalls built into a CMS, WAF rules tuned to specific plugins) had a chance to act. Second, the advisory specifically flagged that risk was highest under mod_php, one of the most common ways PHP is run on shared and business hosting. Third, the PHP security team explicitly reserved the right to publish early if evidence of active exploitation appeared — language that signals genuine concern, not routine caution.
Because the vulnerability sits in PHP itself rather than in a theme or plugin, no amount of keeping WordPress, WooCommerce or any other application up to date would have closed the gap. The only real fix was updating the PHP version running underneath everything else — which is squarely a hosting infrastructure responsibility, not a website owner’s.
As soon as the fixed versions were released, our infrastructure team worked through every server on our platform — shared hosting, reseller hosting, and cloud and dedicated server environments alike — to confirm each one was running a patched PHP build. That work is complete: every Rawebs-hosted site is now running a fixed version of PHP, with no action required from customers and no disruption to live sites during the process.
This is one of the practical advantages of managed hosting over unmanaged, self-administered servers: when a fix needs to go out at infrastructure level, across every account, within hours of release, it happens centrally rather than depending on each individual site owner noticing a security bulletin and knowing what to do with it.
If your website is hosted with Rawebs, there’s nothing further you need to do — your sites are already running a patched PHP version. If you manage hosting elsewhere, whether through another provider or on a self-managed server, it’s worth checking directly with that provider that they’ve applied the October 2026 PHP security release, since the vulnerable versions remain exploitable until the update is actually installed.
More broadly, this is a good reminder of why the PHP version underneath a website matters just as much as the application running on top of it. If you’d like us to review your current hosting setup, or you’re considering moving to a platform where this kind of patching happens automatically and centrally, take a look at our business web hosting plans, or get in touch with our support team if you have any questions about this release.
Powered by WHMCompleteSolution