PHP2Shell — the whole story, and what it means for you

A plain-language briefing from HIPAA for Humans. What the vulnerability is, how it was found, how it leaked, and what to do about it.

HIPAA for Humans — protecting your health data

The short version

This week a critical flaw in PHP — the software that runs an estimated 70% of the web — went public and is being actively exploited right now. It's called PHP2Shell. The flaw lets an attacker take over a server without logging in ("unauthenticated remote code execution"), and it can leak data straight out of a server's memory. Cloudflare has measured exploitation attempts climbing into the millions; the U.S. National Security Agency, the U.K.'s National Cyber Security Centre, and even Japan's prime minister have told organizations to patch immediately or take vulnerable sites offline.

The reason this one is different from the usual security scare is not the flaw itself — it's how it was found, and how fast it got weaponized. That's the story worth understanding.

The flaw was known for 22 years — and ignored on purpose

Back in 2004, a security researcher warned that this weakness in PHP could let an attacker read passwords, steal databases, or take over a site. Partial fixes came in 2020 and 2024, but the core problem sat open for two decades. Not because nobody noticed — because actually exploiting it required mind-numbing, precise, tedious work that no human attacker thought was worth the effort.

The industry even had a name for this kind of protection: "security by exhaustion." The lock was pickable; it just took so long that nobody bothered.

AI did the tedious part in two days

This summer, OpenAI (through an initiative called "Patch the Planet") together with security firms Wiz and Calif pointed large AI models at PHP to see what would happen. They didn't expect anything critical. Within about 48 hours the AI had found not one but several working ways in.

In plain terms: one method sneaks a compressed file past PHP's size checks so it unpacks and takes over from the inside; another overwhelms the server to force the exact out-of-memory crash the attack needs, leaving stale data behind — passwords, session tokens, encryption keys — that an attacker can read. Work that was "impractical for a human" became a weekend for a machine. Security researchers are calling it one of the most severe vulnerabilities in software history, and a wake-up call.

And then it leaked before everyone was protected

The careful way to handle a flaw like this is quiet: tell the maintainers, let them ship a fix, then announce it. That window got blown. One security company posted fixes hours before the official disclosure, effectively tipping off attackers. Amazon saw exploit attempts before the announcement. Cloudflare measured thousands of attempts in the 10 hours before disclosure — jumping to millions now. The blunt takeaway: the bad guys don't need to find the vulnerability first — they can weaponize it after the fact. Which is exactly why "patch now" beats "patch when I get to it."

What this means for your organization

For most healthcare organizations, the core systems that hold patient information — your EHR and the major cloud platforms — are run by vendors who patch centrally, and are not the direct exposure here. Where the risk usually lives, if anywhere, is a website or a self-hosted application:

The worry isn't usually the website itself; it's that an attacker could use it as a path toward the sensitive systems behind it.

What to do — this week, not next month

  1. Make a short list of what you run that touches the internet: your website (is it WordPress?), any portal, any self-hosted application, anything with a form.
  2. Ask whoever maintains each one to confirm in writing that PHP, and WordPress core + plugins/themes where applicable, are updated to the current patched versions — today if possible.
  3. If they can't confirm today, take the form or site offline until they can. A day of a "call us to get started" page beats leaving a known, actively-exploited hole open.
  4. Know that "offline" isn't a guarantee if a site was already exposed — this flaw can leak data from memory. If a site that handled sensitive information was unpatched during this window, it's worth a closer look.

The bottom line

This is manageable if you move now and genuinely risky if you wait. If you want a hand thinking through what you run and where the exposure is, we're here for you — that's what HIPAA for Humans is for.