If you have a website for your business, you may have seen worried headlines about the PHP2Shell hack. It sounds technical, and it is, but the question for you is simple: is my website safe, and who needs to do something about it? This guide explains what happened in plain terms, what to check, and what to ask the people who look after your site.
What is the PHP2Shell hack?
PHP is a piece of software that quietly runs behind a huge share of the web. If your site is built on WordPress, Joomla or Drupal, it almost certainly uses PHP. Many bespoke sites and online shops do too.
In October 2026, two serious flaws in PHP were made public under the name PHP2Shell. They had been spotted a couple of years earlier but were not thought to be usable by attackers. Security researchers then found a way to use them, and the PHP Foundation, which looks after PHP, released fixes.
What makes these flaws so worrying is how little an attacker needs. They do not need a password. Nobody has to click a dodgy link or open an attachment. Someone anywhere in the world can, in principle, take control of a server that has not been fixed. Once in, they could steal data, add harmful code or quietly leave a way back in for later.
According to TechCrunch's reporting, large firms took websites offline to patch them, and there were signs some attackers knew about the flaws before the fixes came out.
Why the PHP2Shell hack matters to small businesses
It is easy to assume hackers only go after banks and big retailers. They don't. Attacks like this are usually automated. Programs scan the internet looking for any server that has not been fixed, and they do not care whether it belongs to a national chain or a family-run bakery.
A hacked small business site can be used to send spam, host scam pages, or redirect your visitors somewhere unpleasant. If you take bookings or payments, customer details could be at risk. And if Google spots harmful content on your site, it may warn people away from it, which hurts your search traffic for a while even after it is cleaned up.
Is my website affected?
The important thing to understand is that the fix is not something you install inside WordPress or your website editor. It is installed on the server your website sits on. So the real question is: who looks after that server?
- Shared or managed hosting: your hosting company is normally responsible for updating PHP. Most reputable hosts will have acted quickly, but it is worth asking for confirmation.
- Your own server or virtual server: you, your developer or your IT provider are responsible. Don't assume it has been done.
- An older site nobody has touched in years: this is the riskiest case. Very old versions of PHP may no longer receive fixes at all.
What to do this week
- Ask your host or developer a direct question. Something like: “Has the server running our website been updated against PHP2Shell, and when?” A good provider will give you a clear yes and a date.
- Check which version of PHP your site uses. Your hosting control panel usually shows this. If it is an old version that no longer gets security updates, plan to move to a supported one.
- Make sure you have a recent backup stored somewhere other than the server itself, so you can restore a clean copy if needed.
- Update everything else while you are at it. WordPress itself, themes and plugins are not the source of this problem, but keeping them current closes other doors.
- Change key passwords for your hosting account and website admin if you have any doubt at all.
If you are not sure who looks after your hosting, that is worth sorting out now, not just for this problem but for the next one. Our hosting and maintenance service exists for exactly this kind of job.
Signs your site may already have been hit
Because some attacks seem to have started before the fixes were released, it is sensible to look for warning signs even if your server has now been updated:
- Admin users on your website that you don't recognise.
- Pages, posts or files you didn't create, especially ones full of spammy links.
- Visitors being sent to other websites.
- Your site suddenly running slowly or falling over.
- Odd results when you search Google for your business name.
- A warning from your host or from Google about your site.
If you see any of these, don't just delete the odd file and move on. Attackers often leave hidden ways back in. Ask a professional to check the whole site properly.
Don't forget the boxes in the cupboard
PHP is not only used on websites. It also turns up inside some routers, network storage boxes and security equipment such as firewalls. These are easy to forget because they just sit there working.
Check whether the makers of your office equipment have released updates, and install them. If you have a device that is so old it no longer gets updates, it may be time to replace it. Our five-minute security check for small offices is a good place to start.
The bigger lesson
PHP2Shell will not be the last scare of its kind. A lot of the internet runs on older software that is still widely used, and researchers keep finding flaws in it. The businesses that come through these moments calmly are the ones that already know who looks after their website, how it is updated, and where the backups live.
You don't need to become a security expert. You just need someone you trust to keep things patched and to tell you plainly when something needs doing.
Not sure where you stand?
If you would like a second pair of eyes on your website or office set-up, get in touch with our IT support team. We can check whether your server has been updated, look for signs of trouble and explain what we find in plain English.


