Updated October 21, 2026
At a glance
PHP released emergency fixes on October 21 for two critical vulnerabilities known together as PHP2Shell. They can allow remote code execution without a login on an affected PHP web server. Our managed WordPress hosting platform reports that it applied interim protection and installed patched PHP builds on October 21. Customers using older PHP versions should still plan a move to a supported version.
What happened?
CVE-2026-109618 involves corruption when PHP runs out of memory while processing a request. CVE-2026-109619 involves stale internal state that can be reused by a later request handled by the same PHP worker. These are vulnerabilities in PHP itself, not in WordPress or a particular plugin. Updating WordPress, themes, or plugins alone does not fix the PHP runtime.
The PHP project released fixed versions 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Linux distributions may supply backported patches under different package version numbers. PHP 8.1 and older no longer receive normal security releases from the PHP project.
What we did
On October 21, our managed WordPress hosting platform disabled PHP's session upload-progress feature as an interim protection, tested the change for site and upload disruption, and installed patched PHP builds. The interim protection remains in place. The platform is moving a small number of sites on older servers to upgraded servers while keeping that protection active. It reports patched builds for older PHP branches as well, although those branches remain end of life.
We reviewed the PHP security advisory and the hosting-platform update, then published this guidance for our customers. We also checked the separate Uwebbz Hosting portal server on October 21: its application and worker run on Node.js, and no PHP binary or PHP web service was present on that host. This portal check does not establish the PHP version of an individual WordPress site. We have not performed an independent site-by-site patch or compromise audit.