Updating software is normally the safe thing to do. This time, the risky moment was the update itself: a flaw in WordPress, the platform behind countless shop, café and consultancy websites, gave attackers a brief opening while a site was installing a new version. The US Cybersecurity and Infrastructure Security Agency (CISA) now says that opening is being used.

What happened

On 28 October 2026 the WordPress project released WordPress 7.1.4, a security release fixing a range of issues. The most serious was described as a weakness in the upgrade process "which can lead to remote code execution during the upgrade window". Remote code execution means an outsider can make your web server run their own programs, which in practice means taking control of the site.

WordPress's security advisory explains how. During a full core update, WordPress unpacked the new files into a predictable folder that could be reached from the web. An attacker who timed a request just right, winning a "race" against the update, could run code on the server without logging in. The flaw was found and reported by researcher Umut Bayram.

The issue is tracked as CVE-2026-119977. The CVE record, filed by the security firm Wordfence, rates it 8.1 out of 10 (high), with "high" attack complexity: the attacker has to hit the short window while an update is running. It affects WordPress versions 4.7 through 7.1.3.

The fix shipped in 7.1.4, and WordPress backported it to every older branch back to 4.7 (for example 7.0.8, 6.9.11 and 6.8.12). The project reminds users, though, that "only the most recent version of WordPress is actively supported."

On 3 November CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalogue, its list of bugs with evidence of real-world attacks, and gave US federal agencies until 6 November to fix it. CISA has not published details of the attacks, and the catalogue lists ransomware use as "Unknown".

Why it matters

A small business website is rarely a target in its own right. It is a target because it is easy to find and often forgotten. Attackers scan the internet automatically for sites running a vulnerable version, and a hijacked site can be used to host scams, spread malware to visitors or steal what customers type into forms.

The harder question is who is responsible. Many small firms assume their web host or the agency that built the site keeps it updated. Some do; many contracts say nothing about it. And a site that was built years ago and never touched may be on an old branch that only receives fixes as a courtesy.

What it means for you

At home: if you run a personal blog or club site on WordPress, log in, open Dashboard → Updates and make sure you are on 7.1.4 or the patched release for your branch.

If you run a small business:

  • Check your site's WordPress version today, or ask whoever manages it to confirm in writing that it is patched.
  • WordPress says sites that support automatic background updates will start updating on their own. Confirm that these are switched on rather than assuming it.
  • Agree, in your contract, who applies updates and how quickly: you, your web host or your agency.

If you work in IT or at an MSP:

  1. Inventory every client WordPress site, including ones built by third parties, and record the version and branch.
  2. Move sites to 7.1.4 (or the patched release on their branch) and plan upgrades off old branches.
  3. Run core updates in a maintenance window and review the site afterwards for unexpected files or admin accounts.
  4. Treat the KEV listing as a priority signal. CISA's deadline binds only US federal agencies, but it encourages every organisation to manage vulnerabilities by risk, and a bug under active attack is the top of that list.

The bottom line

The fix is ready and, on many sites, already applied automatically. The real risk is the site nobody owns: an old install on a forgotten branch with no one checking. Find out today who looks after your website's updates, and make sure they have done it.

This article summarises and comments on the sources listed below. It is general information, not legal or professional advice.