中文Imagine waking up to find your company website simply gone. Not hacked with a defaced homepage — just dark. That is what happened this week to a string of printing and packaging suppliers around the world, all because of a flaw in a piece of software most of us never think about: PHP.
If you have never heard of PHP, you are not alone, but you almost certainly rely on it. It is the engine under the hood of roughly 70% of the world’s websites, according to data cited by Cloudflare. When two critical vulnerabilities surfaced on 21 October that could let an attacker run code on a server remotely — no login needed — the internet held its breath. The UK’s National Cyber Security Centre (NCSC) told organisations to patch immediately, and if they could not fix it fast, to take systems offline entirely.
Then the dominoes fell. Through yesterday afternoon, the websites of several industry suppliers and manufacturers went inaccessible for a stretch: Koenig & Bauer, Komori Europe, Mimaki Europe, Sappi, Agfa, Mitsubishi Heavy Industries and Whistl. All are back up now, but for a few tense hours their digital front doors were closed. Government sites in Scotland, Finland and the Netherlands were pulled as a precaution. Even the UK’s Office for Budget Responsibility site blinked offline before recovering by mid-morning.
Here is the part that should make every print business owner sit up. Matthew Prince, co-founder and CEO of Cloudflare, shared the timeline on X and it is genuinely chilling. In the ten hours before the flaw went public, his network saw thousands of attempts to exploit it. In the 45 minutes after the announcement, that jumped to tens of thousands. Within two hours, hundreds of thousands. Now? Millions. Attackers move at machine speed, and they do not care whether you are a global press manufacturer or a two-person sign shop.
The good news, if you can call it that, is that Cloudflare had quietly deployed web application firewall protections in early October, about nine hours before the public disclosure. Their customers were shielded by default. That is the lesson hiding in plain sight: a decent WAF in front of your site is not a luxury, it is the difference between “we were fine” and “we were down for hours.”
So what should you actually do? First, if your website runs on PHP — and most WordPress sites, including plenty of print company sites, do — make sure your host has applied the latest update. Call them if you are unsure. Second, if you run your own server, patch it now; do not wait for a quiet Friday. Third, consider a WAF or a managed host that handles this for you. And fourth, have a plan for the worst case: offline backups, a way to communicate with customers when the site is dark, and someone responsible for pulling the trigger.
The printing industry likes to think of itself as hands-on, ink-and-steel, far from the abstract world of software exploits. This week proved otherwise. Your website is your shop window, your enquiry form, your proofing portal, sometimes your entire order pipeline. When it is gone, so is a chunk of your business.
PHP2Shell will fade from the headlines, but the pattern will not. Vulnerabilities like this appear regularly, and the window between disclosure and mass exploitation is now measured in minutes. The shops that survive the next one will be the ones that treated patching as routine, not as a fire drill. Do not be the name on the list of sites that went dark. Patch tonight.
Source: Printweek
