On Wednesday, October 21, we built, tested, and deployed PHP’s newly released security fixes in our hosting environment. The rollout covered four supported PHP branches. Final verification was complete by 10:40 a.m. Eastern.

At the time we needed to act, the ready-to-install updates for our server environment were still unavailable. The PHP project had released the corrected source code, so we built the packages ourselves.

What needed updating

PHP is the software that runs WordPress and WooCommerce behind the scenes. Wednesday’s two critical advisories, CVE-2026-109618 and CVE-2026-109619, described vulnerabilities that could allow an attacker to execute code on an affected server. Fixing them required updating PHP itself.

Getting the fixes into production

Normally, an update reaches a server after a package maintainer takes the project’s source code and prepares it for a particular operating system. That process keeps installations consistent and makes future updates easier to manage. It can also leave a gap between a fix being released and that fix appearing in the server’s normal update feed.

We had the access and technical capability to close that gap. We downloaded the PHP project’s official releases, checked the downloads against its published checksums, and compiled packages that matched our existing configuration. We preserved the settings, extensions, and service connections our websites already depended on. The fixes came from the PHP team; our work was building, validating, and deploying them for our environment.

Testing and verification

Before deployment, we ran focused regression tests on each of the four PHP branches and checked extension compatibility, production configuration, and isolated PHP services. All 24 selected regression tests passed. We then updated one branch at a time, checking the service after each restart.

After installation, we verified the PHP processes actually serving requests were running the patched versions. We also checked 126 URLs across the environment and confirmed that their final HTTP responses matched the pre-update baseline. An independent review checked the built packages and the live deployment results.

The rollout did involve a brief interruption: one service restart produced request errors during a two-second window. The subsequent checks confirmed service recovery, with no continuing related errors found in the reviewed interval.

Why we could act quickly

What made this response possible was knowing the environment and being able to work directly on it. We could identify which PHP versions served which sites, build compatible updates, test them, and verify the result ourselves. We also packaged the changes so later official updates could replace them through the normal update process.

For a store owner, the practical benefit is having someone take responsibility for the work behind the website. You shouldn’t have to track PHP releases or figure out whether a server update actually took effect while you’re helping customers and running your shop. That work is part of how we look after the websites in our care.

← All News