Your website can look perfectly fine and still be running on software that nobody is fixing any more.
Every website sits on layers of software: the server and the programming language it runs (for most charity sites, that's PHP), the content management system (CMS) such as WordPress, and the plugins and themes added on top. Each layer gets security fixes for a limited time. When that time runs out, it reaches "end of life".
Your site won't switch off that day. What changes is that the next time a serious flaw is found, nobody will fix it, and your website and the supporter data behind it stay exposed.
This guide explains how to check where your site stands, the dates that matter right now, and how to choose your next step. It's written for the person who has to make the decision, not for developers.
Why "it still works" isn't the same as "it's safe"
On 21 October 2026, the PHP project released urgent fixes for two critical flaws, nicknamed PHP2Shell, that let attackers run code on unpatched servers without logging in. Within days, they were being used in real attacks. Websites on supported PHP versions could be fixed with a routine update. Websites on old versions had no official fix at all.
That's the pattern every time: supported software gets fixed quickly, unsupported software doesn't, and attackers read the same security notices you do. Read our PHP2Shell guide for the full story.
The key PHP dates
PHP is the layer most charities never think about, and the one most likely to be out of date.
| PHP version | Security fixes | What to do |
|---|---|---|
| 8.1 and older | Ended | Upgrade as a priority |
| 8.2 | Until 31 December 2026 | Plan your upgrade now |
| 8.3 | Supported | Keep it updated |
| 8.4 and 8.5 | Supported | Keep it updated |
WordPress recommends PHP 8.3 or newer. If your site is on 8.2 or older, aim straight for 8.3 or 8.4 so you're not repeating the exercise in a few weeks.
WordPress: the core is rarely the problem
WordPress handles security well. Its security updates usually install automatically, and it doesn't publish end-of-life dates for its main versions the way some platforms do. WordPress.org only actively maintains the latest release, so staying on it is what keeps the core itself safe.
The risks are almost always around it:
- Plugins and themes that are no longer maintained. A plugin that was useful in 2019 may not have been updated since, because its developer moved on or the company closed. It keeps working, so nobody notices. This is the most common way into a WordPress site.
- Automatic updates switched off. Sometimes for a good reason years ago, then forgotten.
- An old PHP version on the server. Updating WordPress doesn't update PHP. That's down to your host or whoever manages your server.
- Old admin accounts. Former staff, agencies and volunteers who still have logins.
A quick test: open the Plugins page in your WordPress admin and look for any plugin that hasn't been updated in over a year, or whose page on WordPress.org says it has been closed. Each one deserves a closer look.
How to check what your site runs
- WordPress: go to Tools → Site Health → Info. The WordPress and Server sections show your versions, and the Status tab flags anything WordPress thinks needs attention.
- Any other website: check your hosting control panel, or ask your developer.
- Not sure, or no admin access? Ask your web supplier or host: "Which CMS version and PHP version are we on, and when do they stop getting security fixes?" A good supplier will answer straight away.
What end of life does and doesn't mean
| It does mean | It doesn't mean |
|---|---|
| No more security fixes for that version | Your site goes offline |
| Plugins gradually stop supporting it too | You've been hacked or done anything wrong |
| Your risk grows with every new security notice | You must rebuild from scratch |
| Insurers, funders and auditors may ask questions | You have to decide everything this week |
Your three realistic options
1. Update and tidy up
For most sites, this is all that's needed. Move PHP to a supported version, update WordPress, replace any abandoned plugins, remove ones you don't use, and test the pages that matter most, especially donation and sign-up forms.
Best for: sites that work well for your team and just need bringing up to date.
2. Rebuild on solid foundations
If your site depends on a lot of abandoned plugins, heavily customised code or a theme nobody can safely update, patching it can cost more over time than rebuilding it properly. A rebuild is also a chance to fix accessibility, speed and the editing experience at the same time.
We'll only recommend a rebuild if the numbers and your team's needs support it. Often, updating is the right call.
Best for: sites with high maintenance costs, frustrated editors, or a redesign already on the horizon.
3. Buy time, carefully
If you're mid-way through a funding cycle, you might need a few months. Extra protection such as a web application firewall, tighter logins and closer monitoring can reduce risk in the meantime. It's a bridge, not a plan.
Best for: organisations that need time to plan and budget properly.
Five questions that will make the decision for you
- How many plugins do we rely on, and are they still maintained? Abandoned ones will need replacing whichever route you choose.
- How much custom code do we have? A few small tweaks keep updating simple. Lots of bespoke features make it a bigger job.
- What does our site connect to? Donation platforms, CRMs, email tools and event systems all need testing after any change. See our integrations service.
- Who edits the site, and do they like it? If editors avoid the site because it's hard to use, that's a cost too.
- Who is responsible for updates? If the honest answer is "we're not sure", that's the first thing to fix.
How we approach a website health check
When a charity asks us for help, we start with a short, fixed-scope review before recommending anything:
- Version and patch audit: your CMS and PHP versions, their support dates, and whether recent security releases have been applied.
- Plugin and theme review: each one checked for maintenance, compatibility and known security issues.
- Custom code check: anything bespoke reviewed for what will and won't survive an update.
- Integration map: what your site sends to and receives from other systems, so nothing breaks quietly after the change.
- Clear recommendation: update, rebuild or bridge, with the reasoning, risks and a costed plan in plain English.
You keep the report whatever you decide. Find out more about our hosting and ongoing support.
Your checklist for this week
- We know which CMS and version our site runs
- We know which PHP version our hosting runs, and it's 8.3 or newer
- Automatic security updates are switched on, or someone applies them
- We've checked our plugins and themes for abandoned ones
- We've removed logins for people who no longer need them
- We have a recent, tested backup of the site and database
- We know who is responsible for updates, and they've confirmed it
Frequently asked questions
Will Google penalise our site for running old software?
Not directly. But a compromised site can be flagged as unsafe in search results and browsers, which hurts traffic and trust far more than an old version number.
Can updating PHP break our site?
It can, if old plugins or custom code rely on features newer PHP versions have removed. That's why it's worth testing on a copy of the site first. A good host or developer will do this as a matter of course.
Does running unsupported software affect our data protection duties?
UK GDPR requires appropriate technical measures to keep personal data secure. If your site holds supporter, donor or service-user data, running software that no longer receives security fixes is a risk your trustees should know about and record a decision on.
Do you only work with sites you built?
No. Many of the sites we review were built by someone else. We'll work with what you have.
A deadline, not a crisis
Support dates are published well in advance, and the options are well understood. Charities that check their versions now have plenty of choice. Those who wait until something goes wrong have much less.
Sources
- Supported PHP versions (php.net)
- WordPress requirements (wordpress.org)
- WordPress 7.1 hosting compatibility (make.wordpress.org)
- Critical Vulnerabilities in PHP Require Immediate Patching (CISA)

