WordPress had two security scares this fall. Here's how to check your site

Short answer

Two separate flaws hit WordPress sites this fall. PHP2Shell (October 21) is in PHP, the language WordPress runs on, and only your host can fix it by updating PHP. CVE-2026-119977 (November) is in WordPress itself and is fixed in WordPress 7.1.4. Check both versions in Tools > Site Health > Info, and ask your host when PHP was last updated.

If your website runs on WordPress, two separate security problems landed on it this fall, three weeks apart. Most owners we talk to heard about neither. Here’s what happened, in plain English, and the five-minute check to see where your site stands.

Two flaws, two different fixes

Oct 21PHP fixes PHP2Shell. Your host has to install it.
Oct 28WordPress 7.1.4 fixes a flaw in WordPress itself.
Nov 3The US cybersecurity agency lists the WordPress flaw as under attack.
Dates from php.net, wordpress.org and cisa.gov.

First, the part almost nobody explains

A WordPress site is two layers. WordPress is the part you log into. Underneath it is PHP, the programming language your hosting company runs so WordPress can work at all.

When you click “Update” in WordPress, you update the top layer. You don’t touch PHP. That’s your host’s job, and plenty of hosts are slow at it. This matters because the first problem this fall was in PHP, not WordPress.

October: PHP2Shell

On October 21 the PHP project released fixes for two flaws, CVE-2026-109618 and CVE-2026-109619, which security researchers nicknamed PHP2Shell. The PHP team rated both 9.2 out of 10 and said either one could let an attacker run their own code on a server without logging in. Their advisory mentions a demonstrated exploit, and security firms reported attack attempts soon after.

The fixed versions are PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Here’s the catch for small businesses: the PHP project says PHP 8.1 and older no longer get updates from them at all. Plenty of small business sites still run on those. Some hosts patch old versions themselves. Some don’t.

There’s more coming, too. On November 18, PHP announced another critical security release for November 19.

November: a flaw in WordPress itself

The second problem is in WordPress, tracked as CVE-2026-119977. It’s a timing weakness in the way WordPress updates itself: while an update is running, an attacker can sneak their own code in. It affects WordPress 4.7 through 7.1.3.

WordPress fixed it in 7.1.4 on October 28. On November 3, the US Cybersecurity and Infrastructure Security Agency added it to its list of flaws known to be used in real attacks. Wordfence, a WordPress security company, reported attack attempts starting the same day the fix came out.

One odd detail: because the weakness is in the update process, a researcher warned that sites can be hit while they install the fix. If someone manages your site, ask them whether they took that into account.

Sites on older WordPress branches are getting their own fixes. As of today, WordPress says those “will ship as they become ready.”

Check your own site in five minutes

Four checks, in order

  1. 1WordPress versionDashboard, then Updates. You want 7.1.4 or newer.Takes 30 seconds
  2. 2PHP versionTools, then Site Health, then Info, then Server.Takes 30 seconds
  3. 3Compare8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer is fixed. 8.1 or older gets no official fix.Takes a minute
  4. 4Ask your hostEven if the number looks old, they may have patched it. Get it in writing.One email
Dashboard paths are for a standard WordPress install. Some hosts also show the PHP version in their control panel.

If you can’t log into your own WordPress dashboard, that’s worth fixing on its own. Whoever built the site should hand you an admin login.

What to send your host

Copy this, fill in your domain, and send it:

Email to your hosting company

Hi, my site is yourdomain.com.
  1. Which PHP version is it running?
  2. Has it been updated for CVE-2026-109618 and CVE-2026-109619 (the October 21 PHP fixes)?
  3. If my PHP version is 8.1 or older, what does it take to move to a supported version?

Thanks

A good host answers all three the same day.

Should you leave WordPress?

Not because of this. Every platform has flaws, and WordPress shipped its fix to every site set to update itself. A WordPress site that gets updated, on a host that patches PHP quickly, is in decent shape.

The honest question is whether anyone is actually doing that for you. The way this usually goes wrong is a site that was built once and left alone: nobody owns the updates, the plugins fall behind, and the owner doesn’t have the login.

For what it’s worth, the sites we build don’t run PHP and have no public login page, so there’s no plugin list for anyone to keep patched. That’s one reason we build them that way. It’s not the only right answer. If you’d rather stay on WordPress, we’ll tell you what to ask whoever maintains it. If you’re weighing a move, our website page covers what comes with you from WordPress, Webflow, Squarespace or Wix.

Sources

Questions

Was my WordPress site hacked?

These flaws don't mean it was. They mean it could be if the fixes aren't installed. Signs of trouble are new admin users you didn't add, pages you didn't write, or your host emailing you about malware. If you see any of those, call your host or a security company today.

I updated WordPress. Am I covered?

For the WordPress flaw, yes, if you're on 7.1.4 or newer. For the PHP flaw, no. PHP is updated by your host, not by the WordPress updater.

How do I see my PHP version?

In your WordPress dashboard, go to Tools, then Site Health, then the Info tab, and open Server. The PHP version is listed there. Your hosting control panel shows it too.

My PHP version is 8.1 or older. What now?

The PHP project no longer sends updates for 8.1 and older. Some hosts patch old versions themselves, so ask yours directly, and ask what it would take to move to a supported version.

Do I need to leave WordPress?

No. A WordPress site that is kept updated, with a host that patches PHP quickly, is fine. The real question is whether anyone is doing that for you.