Welcome back to The Security Signal, our biweekly dispatch on what actually matters in security and compliance.

In this issue

  1. The PHP flaw that took down sites from Wikipedia to government portals

  2. Why “we didn’t know we were running it” is the real risk

  3. How Latitude Health built SOC 2 and HIPAA on one foundation

Let’s get into it.

01. SECURITY & TRUST

PHP2shell: the flaw hiding in plain sight

Thankfully, AI found it first.

  • ~10 years. A serious flaw sat inside PHP, which powers WordPress, Wikipedia, and countless online shops, for about a decade. Researchers at Wiz and Calif pointed AI tools at it and found two critical bugs that could let attackers take over web servers. One researcher called it “the most serious vulnerability I’ve ever found.”

  • Oct 21. When the alert went out, Wikimedia pulled systems offline, government sites in Finland and the UK went dark, and SoftBank in Japan even paused its earthquake alerts while it patched.

  • Unplug. The NSA’s advice was blunt: if you can’t patch now, unplug.

  • Millions. Cloudflare saw thousands of exploit attempts before the flaw was even announced, and millions after. No successful attacks were reported in the first days, but experts expect more tries now that the details are public.

02 · THE COMPLIANCE APPROACH

You can’t patch what you don’t know you’re running

The PHP fix itself is simple; experts compared it to running a Windows update. The hard part is knowing where PHP lives in your business. It’s not just in websites. Researchers point out it often hides in network equipment, load balancers, and admin panels that get overlooked during incidents like this.

This is exactly where compliance pays off. Teams with an up-to-date inventory of their systems and vendors could answer “are we affected?” in minutes. Everyone else spent the week guessing.

What to check this week

✅ Know your stack: list every system, site, and device that could be running PHP.

✅ Ask your vendors: if a hosting provider or agency runs your site, confirm they’ve applied the PHP fix. Updating WordPress plugins alone won’t solve it.

✅ Have a plan for “take it offline”: decide in advance who makes that call and how fast.

✅ Watch for phishing: scammers are already using incidents like this as bait.

03 · CUSTOMER CASE STUDY

How Latitude Health built SOC 2 and HIPAA on one foundation

Latitude Health uses AI to take the busywork out of utilization management, automating about 75% of manual tasks so health plans and providers can approve care faster. But in healthcare, great tech isn’t enough. When you handle sensitive patient data, you have to prove you can protect it, and early enterprise customers wanted that proof fast.

So Latitude teamed up with ComplyJet. Within a few days, ComplyJet took care of the non-engineering work (policies, risk assessments, training, evidence workflows) so the engineers could keep building. Over the next month, the team connected their cloud infrastructure, and ComplyJet lined up an auditor and kept the process moving.

The result? SOC 2 Type 1 within a few months, followed by a full Type 2. When a customer contract required HIPAA, they added that too, on the same foundation instead of starting over.

❝

We not only achieved compliance but also gained confidence in our overall security posture.

— Chuck Feerick, CEO, Latitude Health

PHP2shell won’t be the last decade-old bug that AI brings to light. The teams that come through these moments calmly aren’t luckier. They just know what they run, who runs it for them, and what to do when the alert lands.

For more breakdowns like this on security, AI & compliance insights: