
Most small business websites that get broken into aren't hit by anything clever. The attacker uses a flaw that was disclosed weeks or months earlier, in a plugin, a theme, a PHP library or a control panel, and the fix was already sitting in an update nobody installed. The breach happens in the gap between "a patch exists" and "the patch is applied." That gap is what website patch management is for. It isn't about clicking "update all" more often. It's about knowing what software your site actually runs, who is responsible for each piece, which fixes matter this week and which can wait, and how to apply them without taking down a checkout page on a Friday afternoon. This guide covers the whole website stack, not just the office laptops that most patching advice is written for. It also covers the deadline Canadian site owners face right now: PHP 8.2 stops receiving security fixes on 31 December 2026. What website patch management actually means Website patch management is the repeatable process of finding, prioritizing, testing, applying and verifying security updates across every layer of software that serves a website, from the server's operating system to the last plugin. The distinction from "keeping things updated" matters. Updating is an act. Patch management is a system with four properties that a habit lacks: An inventory. You know every component and its version, including the ones you forgot you installed. Every layer has a named person or provider responsible for it. Fixes are applied within a target window that depends on risk, not on when someone remembers. Someone checks that the patch actually landed and the site still works. Take any one of those away and the system degrades into hope. A business can have automatic updates switched on and still run a vulnerable plugin for a year, because that plugin was removed from its marketplace and will never ship another update. Auto-update can't install a fix that doesn't exist. Security patching is one part of a broader defensive posture. If you want the bigger picture of why the public website has become the place attackers aim first, see why your website...

