- 43% of UK businesses reported a cyber breach or attack in the past year. For small businesses it was 46%.
- Most attacks are automated and use known holes: old software, outdated plugins and stolen passwords.
- PHP 8.2 stops getting security fixes on 31 December 2026. Versions 8.1 and older already get none.
- Most of the fixes are one-off jobs for your web person or host, not ongoing work for you.
Website attacks in 2026: what the figures say
Several big reports came out this autumn, and they all point the same way: attacks keep coming, and most of them get in through doors that could have been closed.
- 43% of UK businesses reported a cyber security breach or attack in the last 12 months. For small businesses it was 46%, and for micro businesses 42%. Phishing was the most common kind, hitting 38% of businesses. (UK government, Cyber Security Breaches Survey 2025/2026, published April 2026.)
- 1,831 attacks were reported to the UK's National Cyber Security Centre between September 2025 and August 2026. 337 needed the NCSC's help, and 80 were nationally significant. The NCSC says attackers "routinely exploited known vulnerabilities in internet-facing systems, used stolen credentials, and employed social engineering". (NCSC Annual Review 2026, published 3 November 2026.)
- 11,334 new security holes were found in WordPress add-ons and themes in 2025, 42% more than in 2024. 91% were in plugins. 46% had no fix from the developer when they were made public. For the most heavily attacked holes, the typical time from disclosure to mass attacks was 5 hours. (Patchstack, State of WordPress Security in 2026.)
- 18.2 million DDoS attacks (floods of traffic meant to knock sites offline) were blocked by Cloudflare in July to September 2026 alone, about 8,200 an hour. (Cloudflare DDoS Threat Report, Q3 2026.)
None of this means someone is sitting down to attack your business in particular. Small business websites are mostly hit by automated scripts that scan thousands of sites for one known weakness, then break into every site that has it. Being small doesn't hide you. Being up to date does.
What we found on 249 real business websites
In November 2026 we checked the websites of 249 UK IT support companies, the firms other businesses pay to keep their computers secure. We looked only at what any visitor can see: no logins, no break-in attempts. If anyone's website should be in good shape, it's theirs. Many weren't, and the same gaps turn up on small business websites of every kind.
| What we checked | What we found |
|---|---|
| Valid HTTPS (the padlock) | 8 of 249 sites didn't have it working |
| Security headers (browser settings that block common attacks) | 159 of 248 had at most one of the six basic ones |
| WordPress version visible to anyone | 119 of 142 WordPress sites showed it |
| Website software behind on updates | 18 of the 69 sites where we could tell |
| Plugins with a publicly listed security hole | 56 of 142 WordPress sites ran at least one |
| PHP version visible to anyone | 44 of 249 sites showed it |
| PHP version that no longer gets security fixes | 10 of those 44 |
| Email protection against fake emails sent in your name (DMARC) | 88 of 249 had none switched on |
A listed security hole doesn't always mean the site can be broken into. Sometimes the hole only matters with a certain setting. But it's exactly what the automated scripts look for, so it's worth closing.
The PHP deadline: 31 December 2026
PHP is the language most business websites run on behind the scenes, including every WordPress site. Each PHP version gets security fixes for a few years, then stops. After that, any new hole that's found stays open for good.
| PHP version | Security fixes until |
|---|---|
| 8.1 and older | Already ended (8.1 on 31 December 2025) |
| 8.2 | 31 December 2026, in about seven weeks |
| 8.3 | 31 December 2027 |
| 8.4 | 31 December 2028 |
| 8.5 | 31 December 2029 |
Source: php.net, Supported Versions.
Of the 44 sites in our check that showed their PHP version, 10 were already on versions with no security fixes, as old as PHP 7.2. Another 3 were on 8.2, which joins them at the end of the year.
What to do: ask your host or web person which PHP version your site runs. If it's 8.2 or older, ask them to move it to 8.3 or newer. On most hosting it's a setting in the control panel. The real work is checking that your theme and plugins still work afterwards, so do it on a test copy first if your site is complex. Don't leave it until the last week of December.
While you're there, ask them to stop the site announcing its PHP version to every visitor (the X-Powered-By header). It doesn't fix anything on its own, but there's no reason to hand attackers a shortcut.
What to fix before the end of the year
You don't have to become a security expert. Most of these are one-off jobs for whoever looks after your website or hosting. Send them this list.
- Move to a supported PHP version (8.3 or newer), as above.
- Update WordPress, plugins and themes, and turn on automatic updates for security releases. Delete plugins and themes you don't use: switched off isn't enough.
- Replace plugins nobody maintains any more. If a plugin hasn't been updated in over a year, or the developer has closed it, a fix may never come.
- Turn on two-factor login for every account that can change the site, and remove old accounts: former staff, old agencies, freelancers.
- Switch on DMARC for your email domain. It stops scammers sending emails that look like they're from you, and that's how a lot of phishing gets in. Start in "report only" mode, then tighten it once your real emails pass.
- Add the basic security headers. They're small settings on the server or in your CDN, and they block whole kinds of attacks in the browser.
- Check your backups, and make sure a copy is kept away from your web server. Test that one can actually be restored.
For the full list, with how often to check each one, see our website security checklist.
How NetNav helps
A NetNav scan checks the things in this article from the outside, the same way an attacker's script sees your site:
- Software versions: whether your PHP version is still getting security fixes, whether WordPress is up to date, and whether any plugin you run has a known security hole or has been closed by its developer.
- HTTPS: a missing, invalid or soon-to-expire certificate, and old encryption settings.
- Security headers: which ones are missing, and which ones matter most.
- Email protection: whether SPF and DMARC are set up to stop people faking your emails.
Each problem becomes a task that says why it matters and what to ask your web person to do. Once it's fixed, the next scan shows it's done.
If you think you've already been hit
Warning signs include visitors being sent to other websites, pages in Google you didn't create, new admin users, or a security warning in the browser or in Google Search Console. Don't start deleting files. Follow our guide to fixing a hacked website.
Questions
Are small businesses really targeted by hackers?
Rarely by name. Most attacks are automated: scripts scan thousands of websites for one known weakness, such as an old plugin version, and break into every site that has it. 46% of UK small businesses reported a breach or attack in the past year, according to the UK government's Cyber Security Breaches Survey.
What happens when PHP 8.2 reaches end of life?
From 1 January 2027, PHP 8.2 gets no more security fixes. Your site keeps working, but any new security hole found in PHP 8.2 will stay open. Move to PHP 8.3 or newer before then.
How do I find out which PHP version my website uses?
Ask your hosting company or web developer, or look in your hosting control panel, usually under a "PHP version" or "PHP settings" page. In WordPress, Tools > Site Health > Info > Server shows it too. A NetNav scan also reports it when your server makes it visible.
Is WordPress safe to use for a business website?
Yes, when it's kept up to date. WordPress itself had only a handful of minor security holes reported in 2025. Almost all problems come from plugins and themes that aren't updated, so update regularly and keep the number of plugins small.
Bálint builds the NetNav platform: the agents that check every website, and the rules that turn what they find into a prioritised list of tasks. Every new check is tested on real websites before customers see it, so what NetNav tells you is accurate and its fixes are safe to make. He also writes NetNav’s guides on site speed, security and legal compliance.