Skip to content
Challenge

WordPress vulnerability: patch first, then do the honest maths.

When a WordPress vulnerability hits, patch first, today. Whether you stay on WordPress afterwards is a second question. The single vulnerability does not answer it, your effort across the whole year does.

The reality

The email from your host arrived. And nobody knows who is responsible.

In October 2026 came the next warning: two critical vulnerabilities in PHP, the software WordPress runs on. The media call it "PHP2Shell". Before that, in July, there was a critical vulnerability in WordPress core itself, and WordPress forced the update on every affected site. The agency that built your site is long gone. Your host sends instructions. And you wonder whether this is going to happen every quarter now.

The check

Are you affected? The five-minute check.

Five points in your WordPress dashboard. That is all you need for a first overview.

  1. WordPress version

    In the dashboard under "Updates". Current is at least 7.1.4 (as of November 2026).

  2. PHP version

    Under "Tools", "Site Health", "Info", "Server". Safe are 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer. On 8.1 or older, no patch is coming.

  3. Plugins and themes

    Update everything, delete what is inactive. Unused plugins are a way in too.

  4. Unknown admin accounts

    Check under "Users". An account nobody created is a red flag. Then an update is no longer enough.

  5. Responsibility

    Who installs the next update? If the honest answer is "nobody", you have found your real problem.

The facts

Why this is not a one-off

The WordPress team patches fast. But someone has to react every single time. As of November 2026.

  • 8 security releases

    That is at least how many security updates WordPress shipped in 2026 up to the end of October, six of them since July.

    wordpress.org (opens in new tab)
  • 17 Jul 2026

    WordPress 7.0.2 fixes one critical and one high severity vulnerability. The update was forced on every affected site.

    wordpress.org (opens in new tab)
  • CVSS 9.2

    On 21 Oct 2026, PHP fixes two critical vulnerabilities. According to the PHP project, only the update fully protects you.

    php.net (opens in new tab)
  • 31 Dec 2026

    After that, PHP 8.2 gets no more security updates. Version 8.1 and older get none already today.

    php.net (opens in new tab)
Decision

Patch or switch?

If the first column mostly fits you, switching pays off. Otherwise stay on WordPress and keep it up to date.

  • Switching pays off: With every warning you start looking for who takes care of it

    Patching is enough: Someone is clearly responsible and installs updates within days

  • Switching pays off: Every update is scary because something might break

    Patching is enough: Updates run through without anything breaking

  • Switching pays off: Page builders and 30 plugins make the site slow on mobile

    Patching is enough: A few well-maintained plugins, the site loads fast

  • Switching pays off: You pay for maintenance just to keep the site alive

    Patching is enough: Maintenance costs less than a rebuild in two years

  • Switching pays off: A relaunch is coming anyway

    Patching is enough: The site brings in enquiries and fits your offer

Without WordPress

What changes when you switch

Without WordPress, no server answers every page view with PHP any more. The pages are built in advance and arrive at the visitor ready to go. You edit the content in a separate system, a headless CMS. No website is secure, but there are far fewer parts you have to patch.

Speed is tied directly to this. Many WordPress sites are slow because plugins and page builders do work on every request. If you switch to patch less, you usually get the faster site too. When it pays off is covered in our comparison WordPress alternative: when headless pays off.

The MacNorris approach

How we go about it

  1. Secure what you have: which pages bring enquiries and rankings, which plugins actually do something.
  2. Decide honestly: stay on WordPress with proper maintenance, or switch. We also tell you when staying is the better choice.
  3. Move without losing rankings: redirects, content, sitemap. The checklist is in website relaunch without losing rankings.

Afterwards you run your site yourself, with no dependency on us. We give you a price after a short conversation and an effort estimate.

“The vulnerability is the trigger. The reason is that nobody feels responsible.”
FAQ

What you usually ask us about WordPress vulnerabilities.

No, WordPress core gets patched quickly: by the end of October 2026 there were at least eight security releases. The risk lies in how a site is run: old PHP versions, unmaintained plugins, nobody installing updates. A well-maintained WordPress site is secure enough. One nobody looks after is not.

No. The October 2026 vulnerabilities sit in PHP itself, underneath WordPress. A security plugin only runs after PHP has already processed the request. According to the PHP project, nothing short of the update fully protects you. Your host installs it, or you do it in your hosting panel.

No. A PHP update fixes the PHP vulnerability, a new system does not. Switching pays off if you never know who is responsible when the next vulnerability hits, if the site needs a rebuild anyway, or if maintenance costs more than it brings. The vulnerability is then the trigger, not the reason.

Not if the move is prepared properly. Every old URL gets a redirect, titles and content of your strong pages stay, and the sitemap goes to Google on day one. Rankings get lost when URLs disappear without a plan. The checklist is in our guide to website relaunches.

Your WordPress site causes more worry than enquiries? Let's talk.

Need help patching? Let us know. We check WordPress, PHP and plugins with you and install the updates. Afterwards you know whether your site is clean.

Thinking about leaving WordPress? Let us know too. We look at what your site does today and tell you honestly whether switching pays off. If it does, we move it without you losing your rankings.

Further reading