Table of Contents

PHP hell is the name developers use for a very specific kind of trouble. The software hidden underneath a website gets too old to be safe, and too tangled with everything else to be changed without something breaking. Most business owners have never heard the term. Many of them know the feeling anyway: a quiet worry that something technical is wrong with the website, and no clear idea who is supposed to deal with it.

This week, that worry got a headline. PHP is the programming language that makes WordPress work. On October 21, 2026, its maintainers released fixes for two serious flaws, nicknamed PHP2Shell, rated 9.2 out of 10 for severity. In plain terms, they could allow someone to take control of a web server without ever logging in. News outlets have been loud about it. Some of the loudness helps and some of it only frightens. This article separates the two, so a PHP hell headline turns into a short list of things you can actually do.

You do not need any technical background to read what follows. Every term is explained the first time it appears, and every section ends with something you can do or ask for.

What Happened to PHP This Week and Why Business Owners Should Care

Picture your website as a shop inside a building. WordPress is the shop itself: the shelves, the signs, the till. PHP is the electrical wiring inside the walls. Nobody admires wiring, and most owners never see it. This week, two faults were found in that wiring, and a repair kit was published on October 21. A repair kit does nothing until an electrician comes and installs it. That electrician is whoever looks after your server, and this is where PHP hell starts for most businesses: nobody is sure who that is.

Was my website actually attacked by PHP Hell?

Nobody outside your hosting company can answer that with certainty, and anyone who claims otherwise is guessing. Public reports do not agree with each other. Amazon said it saw the first exploitation attempt on October 17, four days before the fix existed. Some security publications say real-world damage has not been established. At the time of writing, no named business has been confirmed as broken into because of these flaws.

What is not in dispute is how quickly things move once a flaw becomes public. The 2026 Patchstack report found that for the most heavily attacked WordPress flaws, mass attacks began about five hours after disclosure on average. The sensible reading is that automated scanning of websites started within hours of the news, whether or not anyone has proven a successful break-in. That is a reason to act this week. It is not a reason to panic.

Why did governments and hospitals take sites offline upon PHP Hell showing up?

Reuters and heise reported that several European organisations switched off websites, including the French Interior Ministry, the Dutch national cyber security centre, the Overheid.nl government portal, the Port of Rotterdam and the Charité hospital in Berlin. The NSA and CERT-EU both advised that systems which cannot be updated quickly should be taken offline until they can be. That is a cautious decision by organisations that run very large, very old systems and cannot repair them overnight. It does not mean every website is under attack. It does show that serious institutions treated this as worth an outage, which tells you how seriously to take your own answer to the question further down.

Why Updating Your WordPress Does Not Fix It

The advice most owners have heard is to keep WordPress, the theme and the plugins updated. It is good advice, and it protects against the most common attacks. The security firm Patchstack counted 11,334 new WordPress vulnerabilities in 2025, and 91% of them were in plugins. But those are problems inside the shop. This week's problem is inside the walls, and shop updates cannot reach it.

Putting the site into maintenance mode does not help either. The researchers at Sansec pointed out that the server handles each visit before WordPress gets any say, so a polite "back soon" page sits on top of the same weakness. The only real remedies are installing the repair or switching the server off until it is installed. A flaw like PHP Hell is not limited to WordPress, either. The researcher who found it showed code running on WordPress 7.1.2, Drupal, Joomla, Magento and Laravel, which are all popular website systems.

Who is actually responsible for fixing it?

It depends on where your website lives. The table below shows the three most common situations for Hong Kong businesses, what each one means for you, and the trap that tends to catch owners in each case. If you are unsure which column describes you, the first email in the section on what to do this week will settle it.

Hosting is the most overlooked part of this picture. A hosting company that patches its servers quickly, tests changes first and tells you what it did removes most of the worry. One that does none of those things leaves you carrying a risk you did not know you owned. Our guide to WordPress hosting in Hong Kong explains what a reliable setup looks like, and our managed hosting service is built so that this kind of repair is never left to chance.

Which PHP Version Is Your Website Running

PHP comes in numbered versions, a little like the model years of a car. Each version is supported for a fixed period, and then its makers stop issuing safety repairs. Whether your website is safe this week depends mostly on one number: the version you run. This number is the heart of every PHP hell story, because the older it is, the fewer options you have.

How do I find my PHP version without a developer?

Log in to your WordPress dashboard and open Tools, then Site Health. Click the tab called Info, then open the section called Server. One of the lines there is labelled PHP version, followed by a number such as 8.1 or 8.3. Take a screenshot of that line and keep it. That single image is what your host or agency needs to see, and it takes about two minutes to find. If you cannot log in, or the menu looks different, your hosting company can tell you the same number in one reply.

What does that number mean for my business?

The table below translates the number into plain language. The shares come from WordPress.org usage figures analysed by Digidop on October 22, 2026. They show how many WordPress websites sit in each group, so you can see how common your situation is.

More than a third of WordPress websites sit in the first column. WordPress 7.0, released on May 20, 2026, still runs on PHP 7.4, but it recommends version 8.3 or newer. That gap, between what still works and what is actually safe, is where PHP hell grows quietly for years.

What happens on December 31, 2026 with PHP Hell?

On that date PHP 8.2 loses its official safety support. Websites on it keep working exactly as before. The difference appears the next time a flaw is found: nobody will release a fix for 8.2, and those sites will be in the position the 8.1 sites are in today. Some hosting providers are not waiting. Acquia, a large hosting company, began moving customers from 8.2 to 8.4 on October 1, 2026. If your host has not mentioned a date, ask for one.

Why Upgrading PHP Can Break a Website

If upgrading is the answer, a fair question is why over a third of websites have not done it. The reason is simple and a little uncomfortable. Changing the wiring in a building where people are working is risky. Plugins and themes written years ago may depend on older versions of PHP, and when the version changes underneath them, a form may stop sending, a checkout may fail, or the whole page may turn white. Providers who have seen this happen once often choose to leave things alone forever. That is how a website ends up in PHP hell: every month of delay makes the eventual upgrade bigger and scarier.

What is a staging copy and why does it matter?

A staging copy is a private duplicate of your website on a separate address that the public never sees. Your provider upgrades PHP on the duplicate first, clicks through every important page, and fixes whatever breaks. Only when everything works is the same change made on the real site. It is the difference between rehearsing a surgery and performing it for the first time. Any provider who suggests upgrading the live site directly, with no copy and no backup, is gambling with your enquiries.

Which parts of the website should be checked after an upgrade?

Everything that makes or protects money. That means contact and enquiry forms, checkout and payment, bookings, the English and Chinese language switch, customer logins and the emails the site sends out. A homepage that looks fine is not proof of anything, because the pages that fail first are the ones nobody opens daily. A careful provider tests these on the staging copy and sends you a short report.

What to Do This Week Without Being a Developer in case of PHP Hell

There are three moves, in this order. First, find your PHP version using the steps above. Second, send your host or agency one clear message. Third, decide what happens next based on the answer. None of this requires you to understand code. It requires you to ask, and to keep the reply. Owners who handle PHP hell well are rarely the technical ones. They are the ones who ask early and write everything down.

What should I send my host or agency if I suspect PHP Hell?

Copy this and paste it into an email, changing nothing: "Hello, please confirm in writing which PHP version my website is running, the date it was last updated, and whether the security release of October 21, 2026 has been installed. If my version is 8.1 or older, please tell me your plan and the date for moving to a supported version." A good provider replies within a day or two with specifics. A slow reply, a vague reply or a reply that changes the subject is also an answer, and you now know what it is.

What if the answer is PHP 8.1 or older?

Treat it as urgent, but stay calm and methodical. Ask for a full backup first, then an upgrade tested on a staging copy, then a firm date, ideally within the next few weeks. Be careful with anyone who offers a quick unofficial patch to make the problem disappear. Patchstack specifically warns against unofficial fixes for flaws of this kind, because a home-made patch can introduce new faults or give a false sense of safety. The real solution is a supported version of PHP.

What if the answer is PHP 8.2?

You have more time, but not unlimited time. If version 8.2.35 is installed, the October flaws are closed on your server. What remains is the calendar: support ends on December 31, 2026, so the upgrade to 8.3 or newer needs a date soon. Booking it in November or early December, rather than the last week of the year, leaves room to fix whatever the staging copy turns up.

What if the site needs to go offline while it is fixed?

A short planned outage is far cheaper than a hacked website. If it is needed, ask your provider to show visitors a temporary page that sends Google a "503" signal, which tells search engines the pause is brief and their rankings should be kept. John Mueller of Google has recommended this. A page that simply says "back soon" without that signal can confuse search engines. Remember that such a page protects your reputation but not your server, so the outage only makes sense if the repair happens during it.

How would I know if my website was already attacked?

Some attacks leave visible marks: administrator accounts you do not recognise, pages you never wrote, visitors being sent to other websites, a warning from Google saying the site may be hacked, or a message from your host. Many careful attacks leave nothing visible at all. If your site was running an old PHP version during the past week, it is reasonable to ask a professional to check the server records for unusual activity. That check takes far less time than cleaning up after a break-in. Our WordPress maintenance team does this routinely.

What to Ask Your Host or Agency

The first email gets you the facts. The questions below tell you whether the people behind your website are actually looking after it. You do not need to understand the technical answers. You only need to notice whether the answers arrive, whether they are specific, and whether they sound like people who have done this before.

Which questions separate a careful provider from a careless one?

Ask who by name is responsible for server updates on your website. Ask how soon after October 21 the repair was installed and whether they can show you the date. Ask whether upgrades are tested on a private copy first. Ask whether a recent backup exists, and where it is kept: a backup stored on the same server as the website disappears together with it, so you want a copy somewhere else that you can reach yourself. Finally, ask what the plan is when a PHP version reaches its end date. A provider with a routine will answer in two sentences. A provider without one will talk for five minutes and say nothing.

What answers should worry you?

Be cautious if you hear that WordPress is up to date so you are fine, because that does not address this problem. Be cautious if you hear that the provider never touches the server, that nobody can say which version is running, or that the answer cannot be put in writing. And be cautious about any plan that upgrades the live website directly with no backup and no test. The point of these questions is not to catch anyone out. It is to find out, before an emergency, whether someone competent is on the other end of the line.

What if I cannot answer these questions or do not know who looks after my website?

That is more common than you might think, and it does not mean you did anything wrong. Most owners handed this job to a freelancer, an agency or a hosting company years ago and never had a reason to revisit it. Send the message above anyway. If the reply is silence, jargon or reassurance with no detail, you are entitled to a second opinion, and the sooner the better.

PHP hell will not end with this week's repair. Every PHP version has an expiry date, a new one arrives every year, and the next flaw is only a matter of time. What actually removes the worry is not a single patch. It is having a named owner for the server, a routine for updates, a practice copy where changes are tried first, and a backup you can reach yourself. Businesses that have those four things read headlines like this week's with interest. Businesses without them read with dread. If you want to be in the first group, a solid WordPress hosting and maintenance setup is where it begins.