Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
Free 30-Min Q4 Growth Review — Map Your Plan Before the Holidays. Book Free →
September VIP Review — Let's Map Your Q4 Growth Plan Together.Book Free →
September VIP Review — Let's Map Your Q4 Growth Plan Together. Book Free →
September VIP Review — Let's Map Your Q4 Growth Plan Together. Book Free →
NOW ACCEPTING Q4 AGENCY PARTNERS — Fully Unbranded, Fully Booked Fast. Apply →
NOW ACCEPTING Q4 AGENCY PARTNERS — Fully Unbranded, Fully Booked Fast. Apply →
NOW ACCEPTING Q4 AGENCY PARTNERS — Fully Unbranded, Fully Booked Fast. Apply →

PHP Security Alert (October 2026): What Coaches With WordPress Websites Need to Do This Week

If your coaching website runs on WordPress, there’s something happening this week you should know about. It isn’t a WordPress update, and it won’t show up as a little red notification in your dashboard.

On 21 October 2026, the PHP project released an emergency security fix. PHP is the language that runs WordPress behind the scenes — on almost every WordPress site in the world, including yours.

Here’s what happened, whether you’re affected, and the 5-minute check to do today. No tech jargon, I promise.

What happened, in plain English

PHP fixed two critical security flaws, CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10 for severity.

What they allow is the scary part: an attacker could run their own code on your website’s server without logging in. That’s how sites get hacked, filled with spam links, or used to send malware to your visitors.

According to PHP’s official announcement, all PHP users are “strongly encouraged to update immediately” — and “there are no complete mitigations, updating is the only safe choice.”

It also moved fast. Codeable reported that details leaked before the fix was out, and that Cloudflare saw early attacks the same morning.

Why updating WordPress won’t fix it

This is what catches people out. The problem isn’t in WordPress, your theme or your plugins. It’s one layer below — in the PHP software on your hosting server.

So you can click “update” on everything in your WordPress dashboard and still be exposed. The fix has to happen on your hosting server.

Are you affected? The 5-minute check

  1. Log in to WordPress and go to Tools → Site Health → Info → Server.
  2. Find your PHP version.
  3. Compare it with the patched versions below.
If your PHP version starts with…You’re safe at or above…Notes
8.58.5.12Fully supported
8.48.4.27Fully supported
8.38.3.36Security fixes until 31 Dec 2027
8.28.2.35Security support ends 31 Dec 2026 — plan an upgrade
8.1 or lowerNo official fixEnd of life — upgrade now

Versions from PHP’s announcement and supported versions page.

One catch: some hosts apply the fix without changing the version number you see. If your number looks old, don’t panic — ask your host.

What to do, depending on your hosting

Your hosting typeWhat to do
Managed WordPress hostingUsually patched for you. Confirm with your host.
Shared hosting (most coaches)Check your host’s status page or email, and ask support to confirm the 21 October fix is applied.
VPS or your own serverNobody will patch it for you. Update PHP and restart it today — or get help.

Many big hosts have already moved. GoDaddy, for example, says its managed WordPress hosting is patched, while VPS customers must update PHP themselves. Every host is different, so ask yours.

Copy-paste this to your host’s support chat:

“Hi, can you confirm that the PHP security release from 21 October 2026 (CVE-2026-109618 and CVE-2026-109619) has been applied to my website? My site is [your domain]. Thank you!”

The second deadline: PHP 8.2 ends on 31 December 2026

Even after this week, there’s a bigger date coming. PHP 8.2 stops receiving security fixes on 31 December 2026. After that, any new flaw like this one won’t be fixed for 8.2 sites at all.

WordPress recommends PHP 8.3 or higher (WordPress core team, 2026). Upgrading is usually a few clicks in your hosting panel — but old plugins or themes can break, so do it carefully:

  • Back up your full site (files and database).
  • Update all plugins and your theme first.
  • Test on a staging copy if your host offers one.
  • Switch PHP to 8.3 or 8.4 in your hosting panel.
  • Click through your key pages — home, booking page, opt-in forms, checkout.
  • Test a booking and a form submission to be sure leads still reach you.

While you’re in there: 6 quick website fixes worth doing

A security scare is the perfect moment for a website health check. These also help your Google rankings and bookings:

  1. Delete plugins you don’t use. Every extra plugin is one more door for attackers.
  2. Turn on automatic updates for plugins you trust.
  3. Set up automatic daily backups stored off your server.
  4. Check your site speed on mobile. Slow sites lose visitors and rank lower.
  5. Test your booking link and forms. Broken forms quietly lose leads for months.
  6. Make sure your site has HTTPS — the padlock in the browser bar.

If your site gets visitors but no enquiries, there may be more going on — see 7 signs your website is costing you clients.

Not sure if your site is safe — or don’t want to touch any of this? Book a free website check-in. We’ll confirm your PHP version, check your backups and plugins, and tell you exactly what needs fixing.

The bigger lesson: “set and forget” websites aren’t safe

Most coaches build a website once and never look under the hood again. That works — until a week like this one.

A website is like a car. It needs regular servicing: updates, backups, security checks and speed tuning. A cheap site with no maintenance often ends up costing far more, as I explain in the real cost of a cheap website.

FAQ

If your site runs PHP older than 8.5.12, 8.4.27, 8.3.36 or 8.2.35, it may be — unless your host has applied the fix. Check under Tools → Site Health → Info → Server, and ask your host to confirm.
No. The flaw is in PHP on your hosting server, not in WordPress, so the fix has to be applied by your host or server admin.
PHP 8.2 stops receiving security fixes on 31 December 2026. WordPress recommends PHP 8.3 or higher.
Go to Tools → Site Health → Info, then open the Server section. Your PHP version is listed there.

Don’t want to worry about PHP versions, backups and security patches ever again? Book a free discovery call — we’ll check your site today and keep it updated, backed up and secure, so you can focus on your clients.

Let's build something beautiful together.

Ready when
you are.

"Whether you need strategy, systems, or someone to finally get it done — I'm here."

Book My Free Discovery Call View Services & Pricing