← All stories

PHP security update after PHP2Shell: what your business website needs now

New PHP security fixes have followed the PHP2Shell hack. Here's what they mean for your website, and how to make sure yours is covered.

Grapevine Media teamWeb & IT for small businesses
PHP security update after PHP2Shell: what your business website needs now

After the PHP2Shell hack, a new PHP security update has been released to close the gaps. If your business website runs on PHP, and a great many do, this matters to you. The good news is that fixing it is usually simple. The catch is that the fix does nothing until someone actually applies it to your website.

This guide explains what the update is, how to tell if your site is affected, and what to do next. You don't need to be technical to follow it.

A quick recap of PHP2Shell

We covered the hack itself in an earlier piece, The PHP2Shell hack: what it means for your business website. The short version is that it took advantage of weaknesses in PHP, the software that powers many websites behind the scenes. If you haven't read that yet, it's a good place to start.

Since then, fixes have been released. This article is about those fixes and how to make sure your website gets them.

What is PHP, and why should a local business care?

PHP is a programming language that runs on the server where your website lives. You never see it, but it does a lot of work. When someone fills in your contact form, browses your products or books an appointment, PHP is often what handles it.

WordPress, the most popular way to build a small business website, runs on PHP. So do many online shops, booking systems and customer portals. If your site was built on WordPress or WooCommerce, it almost certainly uses PHP.

Think of PHP like the engine in a van. You might never open the bonnet, but if the engine has a known fault, you still want it fixed before it lets you down.

What the new PHP security fixes do

The PHP team regularly releases updates. Some add new features. Others, like these, are purely about security. They close the holes that attackers have found or could use.

Security fixes are released for the versions of PHP that are still supported. This is important. PHP versions don't last forever. Each one gets a period of full support, then a period where it only gets security fixes, and then it reaches "end of life". After that, it gets no fixes at all, however serious the problem.

So there are really two questions for your website:

  • Is it running a version of PHP that still gets security fixes?
  • If so, has the latest PHP security update been applied?

If the answer to the first question is no, the new fixes won't reach you. Your site will stay exposed until it moves to a supported version.

How to check which PHP version your website uses

There are a few easy ways to find out.

If you use WordPress

Log in to your WordPress dashboard. Go to Tools, then Site Health, then the Info tab. Open the Server section and you'll see the PHP version listed. WordPress may also warn you on the Site Health page if your version is out of date.

If you have a hosting control panel

Many hosting companies let you see and change your PHP version from their control panel. Look for a setting called something like "PHP version" or "PHP manager".

If you're not sure

Just ask whoever looks after your website or hosting. It's a fair and simple question, and they should be able to answer it quickly. Write the version number down so you can check it against the list of supported versions on the official PHP website.

How to apply the PHP security update safely

Updating PHP is usually quick, but it isn't something to rush. Older themes, plugins or custom code can stop working on a newer version. A careful update avoids nasty surprises.

  1. Take a full backup first. That means your files and your database. If anything goes wrong, you can roll back.
  2. Update your plugins and theme. Do this before changing PHP. Up-to-date plugins are far more likely to work with newer PHP versions.
  3. Test on a copy of your site if you can. Many hosts offer a "staging" site for this. Try the new PHP version there first.
  4. Make the change on your live site. Pick a quiet time, such as early morning or after closing.
  5. Check the important pages. Try your contact form, checkout, booking system and anything else customers rely on.

If your site is on managed hosting, your host may apply minor security updates for you automatically. It's still worth confirming. Don't assume.

Signs your website might need attention

Some things suggest your site may be behind on updates:

  • Nobody has logged in to update it for months.
  • The person who built it has moved on and nobody else has the logins.
  • You see warnings in your WordPress dashboard that you've been ignoring.
  • Your host has emailed about old PHP versions.

None of these mean you've been hacked. But they do mean it's time to get things checked. Our five-minute security check every small office should do is a handy companion to this.

Keeping on top of it from now on

One update won't keep you safe forever. New issues will come up, and new fixes will follow. The businesses that stay safest treat updates as routine, like servicing a vehicle, rather than something to deal with only after a scare.

A simple habit helps. Once a month, check that your plugins, theme and PHP version are current. Once a year, check that your PHP version is still supported. Or hand the job to someone who'll do it for you.

Need a hand?

If you'd rather not deal with any of this yourself, that's completely understandable. Our hosting and maintenance service covers PHP updates, backups and testing, so your website stays secure without you needing to think about it. Get in touch and we'll happily check which PHP version your site is running.