Paidmembershipspro
Day 16 after signup
We patched PHP in real time last week. I still messed up.
Here's what we did in the 18 hours after PHP's warning, and what I got wrong.
Why it works
- Open with the security issue and its relevance so readers understand the stakes before getting into the timeline.
- Pair a detailed account of what the team did with a candid admission of what went wrong to make the update feel accountable.
- Close with practical guidance for readers outside the hosted service, rather than making the message only about the company.
How it is built
- Security issue overview
- Response timeline
- Communication mistake
- Process changes
Email copy
Hi [First name], Last week PHP released fixes for two critical security vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Both could let an attacker run code on a web server without logging in. The problem was in PHP itself, not WordPress or Paid Memberships Pro, so the fix had to be installed on the server. If you host with us on PMPro Max, your site was protected before the official patch even went out. But I made a mistake, because we could do even better with our communication. What happened On Tuesday October 21st, the PHP team did something I've never seen them do. They announced an emergency release a day early, with no details: just "two critical vulnerabilities, fixes coming Wednesday." Within hours it was all over developer social media. The issue was even getting mainstream news coverage as governments suggested taking websites offline until the fix was out to be extra safe. Here's what our team did over the next 18 hours: Tuesday night: Our systems team reconfigured how we update PHP and ran dry tests to make sure we'd be able to push the update out as soon as it was available. Around 12:30 AM Pacific: New information showed one of the vulnerabilities was already being exploited. Along with that info were some hints about how the vulnerability worked. So I turned off the PHP setting that attack relies on (session.upload_progress) on every server we manage. That closed the known attack path for one of the two vulnerabilities hours before a fix was released. No customer site used the feature, and nothing went down. Wednesday morning: In case the official packages were slow to arrive, our systems team built and tested our own PHP build process, so we could compile and ship the fix ourselves in about 30 minutes if needed. 9:36 AM ET: PHP published the fix, 23 minutes early. We started rolling it out within minutes, and every server was patched by about 10:00 AM ET. We used AI tools to quickly scan the logs of every site for issues related to the PHP upgrade. We've seen zero PHP errors since. Kim kept a public post updated all morning with the full timeline: https://www.paidmembershipspro.com Where I messed up We waited until everything was patched before telling our hosting customers. The notice said "you're all set, no action needed." That's good news, but the timing was wrong. One of our core values is being open, and part of that means over-communicating about things like this. Plenty of you saw the PHP warning on Tuesday and went to bed wondering whether your site was exposed, while we were working on it quietly. You shouldn't have had to wonder. It's unusual for a security update to come with a big public warning that goes viral like this one did. But even without the hype, I'd want you to get one notice from us as soon as we've confirmed an issue, and then another once we know it's fixed. We should share what we know when we know it. So we're going to start doing that from now on. If you'd rather not get those emails, we will soon have an option in your account settings to opt out of certain notices. Some people don't want the stress, and that's fair. That's why we manage it for you. What we're changing We're updating our processes and tools so PMPro Max customers get notified in real time when we respond to issues like this. Sadly, security updates like these are getting more common, so this needs to be routine, not something we improvise at midnight. We've already started updating our tools so these notices go out automatically as we work through routine and not so routine issues with the sites we host. We don't just wait for updates Installing patches fast is the minimum. We try to get ahead of problems. When we hear rumors of an issue, or our scanners flag something, we look for ways to patch or mitigate it before it reaches your site. We have scanners watching for updates to WordPress core and popular plugins. Those scans kick off alerts for us and automated tools that look for secur