// Blog / News

The WordPress update is the vulnerability

Share

CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 3, with a November 6 deadline for US federal agencies. It is a race condition in WordPress Core's own upgrade process, rated CVSS 8.1, affecting versions 4.7 through 7.1.3, and it allows an unauthenticated attacker to execute code on the server during the brief window while the site is updating itself. The fix is WordPress 7.1.4, released October 28.

Exploitation was observed from around October 30. Wordfence reported blocking 13,095 attacks targeting this vulnerability in a single 24-hour period, which tells you how quickly attention arrived once the patch revealed the bug.

What a race condition means here

Technically it is a time-of-check to time-of-use flaw. In plain terms: during an update, WordPress verifies something and then acts on it, and there is a gap between those two moments. An attacker who hits that gap at the right instant can substitute their own content and have the server run it. They do not need an account.

The practical consequence is unusual. The vulnerable moment is not "while you are running an old version", it is "while you are in the act of upgrading". A site that updates automatically, which is most of them, opens that window on WordPress's schedule rather than yours.

Two weeks, two inverted lessons

On October 19 we covered the Rank Math compromise, where a paid plugin served malware from the vendor's own official download site for eleven hours. The lesson there was that "install only from official sources" failed, because the official source was the compromise.

This one is sharper still: the update mechanism is the vulnerability. Neither is an argument against updating, which remains the single highest-value security habit a small business has, and the sites being hit now are overwhelmingly the ones still on old versions rather than the ones that updated promptly. But together they make a point worth absorbing. Patching is not a magic act that reduces risk to zero while it runs. It is a privileged operation, and privileged operations are worth watching.

What to actually do

  • Check your version today. WordPress admin, At a Glance, or the Updates page. Anything below 7.1.4 needs attention, and 4.7 to 7.1.3 is a very wide net that catches almost every neglected site.
  • Update to 7.1.4 or later. Backports were issued for older branches as they were ready, but only the newest version is actively supported, so moving forward is the better answer than patching in place.
  • Look for leftovers after updating. Advisories specifically suggest checking for unknown PHP files in WordPress directories, and for a stray setup-config.php, which should not be sitting on a live site.
  • If the site was on an affected version and exposed, treat it as possibly compromised rather than fixed. Updating closes the door; it does not evict anyone already inside. The order of operations for a hacked site applies.
  • Confirm who owns this. If you cannot name the person responsible for your WordPress version, that is the finding behind every one of these stories.
  • Keep automatic updates on. Turning them off because of this would be exactly the wrong conclusion. The sites that suffer most are the ones running four-year-old core.

The takeaway

A flaw in the upgrade routine is a genuinely uncomfortable category, because the safest thing you do is briefly the risky thing. The resolution is not to stop updating, it is to be on a current version so the window is short and rare, and to check afterwards that nothing was left behind. Six weeks of WordPress news all reduces to the same question: does anyone own the version number on your site?

Sources:The Hacker NewsBleepingComputer

Can you name the person responsible for your website's version number? We help small businesses get a real owner, current software and a recovery plan that works.

Talk to us

Related