Valentin K · Partner, security & BI

Why Our Sites Don’t Get Hacked Like PHP Servers Do 

Why Our Sites Don't Get Hacked Like PHP Servers Do

In October 2026 the web got a fresh reminder of what running your own server means. Two critical vulnerabilities were published in PHP itself — not in a plugin, not in a theme, in the language runtime that serves roughly three quarters of all websites whose technology can be identified. Both were remote code execution, both were rated 9.2 out of 10, and within five days both were on CISA’s Known Exploited Vulnerabilities list.

This article is not PHP‑bashing. It is about a structural difference between two ways of building websites — and why the difference matters to you as a site owner.

In short

What “php2shell” exposed

The details are worth understanding, because they explain the whole category:

Both require no login, no special plugin — just your PHP worker processing a crafted request. And because the bug sits underneath every PHP application, the patch duty fell on whoever operates each server: hundreds of thousands of hosting companies, agencies and small businesses. The European Union’s cybersecurity agency publicly warned that some sites might need to be taken offline entirely until patched. The fixes landed in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 — but a patch only protects servers that actually installed it and restarted the workers.

That last sentence is the entire problem with self‑managed PHP in one line.

Why classic PHP hosting gets breached so often

PHP’s security story is not that PHP is badly written. It is the operating model:

We wrote before about why we no longer start new projects on WordPress. Security is one of the honest reasons.

The serverless difference

Now the other side. Sites we build are rendered to static output or served from Cloudflare Workers — lightweight isolates that execute your code on Cloudflare’s edge. What disappears from the picture:

The same logic protects the backend: Supabase gives us Postgres with row‑level security instead of a hand‑administered database server with a publicly reachable port.

What serverless does NOT fix

This is where honesty matters, because “serverless” has become a marketing word. The following attack classes are just as real on our stack, and we handle them deliberately:

So the correct claim is narrower and stronger: we have engineered out an entire category of catastrophic breach — the remote takeover of the web server — and we actively manage the remaining risks. That is a much better position than “we patch PHP every time something like php2shell lands”.

If you are on PHP today: a short, sane checklist

  1. Confirm your PHP version — 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or newer — and that the server restarted after the update. Ask your host in writing if you are not sure.
  2. Inventory your plugins and themes. Remove unused ones; update the rest today, not this month.
  3. Check for the aftermath. Unexpected cron jobs, new admin users, odd outgoing traffic — signs of an older compromise that the new patch will not remove.
  4. Decide what the site really needs. A marketing or content site rarely needs a PHP application server in 2026. Moving it to a static or edge stack removes the entire problem class — and usually makes it faster and cheaper. That is exactly the work our modernization service does.

Summary

October 2026 was not an anomaly; it was the routine cost of the classic hosting model. We choose a stack where the vulnerable layer does not exist — and we do the unglamorous work (secrets, dependencies, DNS, review) on the layers that remain. If you want an outside look at where your current site stands, ask us for a free audit — we will tell you plainly what is exposed and what it would take to fix.

Valentin K

Partner, security & BI

Partner at Take the Space. Background in business intelligence and server security; keeps our stacks hard to break into.

All posts by the author →
What happened to PHP servers in October 2026?
Two critical remote‑code‑execution vulnerabilities in PHP itself — CVE‑2026‑109618 and CVE‑2026‑109619, both rated 9.2 out of 10 — were disclosed on October 21, 2026. Both were added to CISA’s Known Exploited Vulnerabilities catalog within days. Because the flaw is in the language runtime, every PHP site on an unpatched server was exposed, and reports estimated that around 1.5 million of 2.6 million PHP hosts were running versions for which no fix had reached them.
Is serverless really unhackable?
No system is unhackable, and we distrust anyone who claims otherwise. Serverless removes an entire class of server‑compromise attacks — there is no long‑lived operating system, no PHP runtime and no writable filesystem to take over — but you still have to protect secrets, dependencies, DNS and your own application code.
We run WordPress. What should we do right now?
First: verify which PHP version your host runs and that it is 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or newer — and that the server was actually restarted after patching. Audit plugins and remove what you do not use. Longer term, consider moving marketing and content sites to a static or edge stack where PHP is not part of the picture at all.
What do you actually do to keep client sites secure?
Static or edge‑rendered output on Cloudflare, no server‑side PHP, secrets in the platform’s secret store rather than in files, least‑privilege API tokens, automated dependency updates, and DNS hardened against takeover. Plus monitoring: we notice when something changes before your visitors do.

Want a high‑performance website?

Let’s discuss how we can help your business grow.