On 21 October 2026, the PHP project released urgent security updates for two critical flaws now known as PHP2Shell.
If your website runs on WordPress or almost any other PHP-based system, this affects you. Five days later, the US Cybersecurity and Infrastructure Security Agency (CISA) added both flaws to its list of vulnerabilities being actively exploited in real attacks.
This article explains what happened in plain English, how to check whether your site is protected, the questions to ask your host, and how we handle security releases like this at Bee Lite.
What happened, in plain English
PHP is the programming language that runs underneath WordPress and a large share of the web. Think of your CMS as the house and PHP as the foundations.
The two flaws, CVE-2026-109618 and CVE-2026-109619, can let an attacker run their own code on your web server without logging in. Security teams call this "remote code execution". It's the most serious category of web vulnerability, because once someone can run code on your server they can:
- read or copy supporter, donor and service-user data
- change your website, including donation pages
- install malware that infects your visitors
- use your server to send spam or attack other sites
Both flaws are rated 9.2 out of 10 on the industry-standard CVSS severity scale. The PHP maintainers were clear that there is no complete workaround: updating PHP is the only safe fix.
Is your website affected?
Every PHP version from 5.4 onwards is affected unless it includes the October fixes. That covers almost every PHP website that hadn't been updated by 21 October, across common server setups including PHP-FPM, Apache with mod_php, php-cgi, LiteSpeed and FrankenPHP.
Your site is protected if it runs one of these versions or later:
| PHP branch | Fixed version | Security support until |
|---|---|---|
| 8.5 | 8.5.12 | Supported |
| 8.4 | 8.4.27 | Supported |
| 8.3 | 8.3.36 | Supported |
| 8.2 | 8.2.35 | 31 December 2026 |
| 8.1 and older | No official fix | Ended |
One important catch: Linux distributions such as Ubuntu, Debian and Red Hat often fix flaws without changing the main version number. Your server might show an older-looking version and still be patched. Don't panic, and don't assume you're safe either. Ask your host to confirm against their own security notice.
If you're on PHP 8.1 or older
The PHP team published minimal source patches for 7.4, 8.0 and 8.1, but there are no official releases for these versions, and your hosting may not have applied those patches. Treat any site on PHP 8.1 or older as vulnerable until it moves to a supported version.
We'd recommend going straight to PHP 8.3 or 8.4 rather than 8.2, because 8.2 stops receiving security fixes on 31 December 2026, only weeks away.
Why updating your CMS isn't enough
This is where many charities get caught out. Keeping WordPress and its plugins up to date is important, but it doesn't touch PHP. PHP lives on the server, and who updates it depends on how you're hosted:
- Managed hosting: your host should have patched it. Ask them to confirm, in writing.
- Shared hosting: usually handled by the host, but some let you choose your PHP version in a control panel, and an old selection stays old.
- Your own server or VPS: unless someone has been contracted to maintain it, nobody is patching it.
- Fully hosted platforms (where you never see a server): the platform manages PHP for you, though it's still worth checking their status page.
How to check your PHP version
- WordPress: go to Tools → Site Health → Info and open the Server section.
- Anything else: check your hosting control panel, or ask your host or developer.
Five questions to send your host or web supplier today
- Have you applied the 21 October 2026 PHP security updates for CVE-2026-109618 and CVE-2026-109619 to our site?
- Which PHP version and build is our site running now?
- If we're on PHP 8.2 or older, what's the plan to move us to 8.3 or newer?
- Have you checked our server for signs of compromise since the flaws were made public?
- When did you last test restoring our site from backup?
A good supplier will answer all five quickly. If you get vague answers, or none, that tells you something too.
How we respond to security releases at Bee Lite
PHP2Shell won't be the last serious vulnerability. What matters is having a routine that works every time, not heroics on the day. For the sites we host and support, this is the routine:
1. Watch
We follow the official security channels for the platforms we run, including php.net, the PHP Foundation, WordPress security advisories, our hosting providers and CISA's exploited vulnerabilities list. We don't wait for a news story.
2. Know what we run
We keep an up-to-date record of the CMS, PHP version and key modules for every site we look after. When a flaw is announced, we can answer "which of our clients are affected?" straight away, without starting an investigation.
3. Patch, critical issues first
Critical, actively exploited flaws jump the queue. Where time allows, we apply the update to a staging copy first. When the risk of waiting is greater than the risk of the update, we patch production directly and test immediately afterwards.
4. Verify
We confirm the fixed version is actually running, then check the journeys that matter most to you, such as donations, sign-up forms and integrations, so a security fix doesn't quietly break fundraising.
5. Tell you
You get a short, plain-English note: what the issue was, whether you were affected, what we did and whether anything is needed from you. You shouldn't have to read about a risk to your site in the press before hearing it from us.
6. Fix the root cause
A security release often shows which sites are running versions close to end of life. We flag those and plan upgrades, such as moving every site off PHP 8.2 before 31 December, so the next emergency is smaller.
Behind all of this sit the everyday basics: automated, tested backups; web application firewall rules; minimal access for every account and API key; and monitoring for unexpected file changes. None of these replaces patching, but together they reduce the damage if something does get through.
Find out more about our hosting and ongoing support.
Your quick security checklist
- We know our current PHP version
- Our host has confirmed the October 2026 PHP fixes are applied
- We're on PHP 8.3 or newer, or have a date to get there
- Our CMS, plugins and themes are up to date
- We have a tested backup from the last week
- We know who to call if our site is compromised
Frequently asked questions
How would we know if our site has been hacked?
Not always easily, which is why prevention matters. Warning signs include unfamiliar admin accounts, pages or links you didn't create, browser or Google warnings, unexpected redirects, and your host reporting unusual activity. If you're unsure, ask for a review rather than waiting.
What if supporter data has been exposed?
Under UK GDPR, a personal data breach must be reported to the Information Commissioner's Office within 72 hours of you becoming aware of it, unless it's unlikely to put people's rights and freedoms at risk. Speak to your data protection lead straight away, and get your server checked by someone qualified.
Is PHP the only software we need to keep updated?
No. Your CMS, plugins and themes all have their own support dates, and plugins can quietly stop being maintained. Read our guide to unsupported software.
Is PHP still safe to use?
Yes. Every widely used language has serious flaws from time to time. PHP's maintainers found, fixed and disclosed these responsibly, and the PHP Foundation has announced further investment in security. The risk lies in running unmaintained versions, not in PHP itself.
Security is a routine, not a rescue
Most charities don't need a security team. They need a supplier with a dependable routine and the honesty to tell them where they stand. If you're not sure that's what you have today, let's talk.
Sources
- PHP 8.4.27 release announcement (php.net)
- PHP 8.3.36 release announcement (php.net)
- Today's PHP Security Release, and How We're Strengthening PHP Security (The PHP Foundation)
- Critical Vulnerabilities in PHP Require Immediate Patching (CISA)
- Supported PHP versions (php.net)

