Skip to main content

WordPress Core Security Flaw: Check Your Version in a Minute

If your website runs on WordPress, open Dashboard, then Updates, and check that your version is the fixed...

Alex

Alex

CEO

November 5, 2026
4 min read
Security alerts

If your website runs on WordPress, open Dashboard, then Updates, and check that your version is the fixed one for its branch: 7.1.4 if you are on 7.1, 7.0.8 on 7.0, 6.9.11 on 6.9, and so on back to 4.7.39. WordPress released the fix on 28 October 2026, and the US cybersecurity agency CISA listed the flaw as exploited on 3 November. The check takes a minute and the update is the normal one-click kind.

The flaw is in WordPress itself, not in a plugin or theme. A site can have every plugin current and still be on an affected core version.

What’s affected

CVE-2026-119977, rated 8.1 (high) on the CVSS 3.1 scale. The National Vulnerability Database entry, written by Wordfence, says WordPress core is vulnerable to remote code execution in versions 4.7 through 7.1.3. Remote code execution means someone outside the site getting the server to run instructions of their choosing. The cause it gives is predictable, web-accessible staging paths used during full-package core upgrades, and it says an attacker needs no login but must act during the upgrade window, the short period while WordPress is installing a new core version. The score includes a “high” attack complexity rating, which reflects that timing condition. CISA classes the weakness as a race condition (CWE-367). See the NVD entry and the WordPress 7.1.4 release post, which lists it as a weakness in the upgrade process reported by Umut Bayram.

Fixed versions, by branch. NVD lists each of these as the first unaffected release: 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31, 4.9.35, 4.8.34 and 4.7.39. On 5 November the WordPress update service was offering each of them for its branch. The release post says the backports to older branches were in progress and would ship as they became ready, so the safe version for your site is the one shown for your branch on the Updates screen, not necessarily 7.1.4. Releases before 4.7 are outside the affected range in the advisory and no longer receive security fixes, so they should be moved to a current version regardless.

On exploitation: CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 3 November 2026, which is the list of flaws it has evidence attackers are using. Its due date for US federal agencies to apply the fix is 6 November 2026. The catalogue entry does not say whether ransomware groups are using it.

How to check in a minute

  1. Log in to your WordPress admin.
  2. Go to Dashboard, then Updates.
  3. Read the current version near the top of the page. If an update is offered, run Update Now.

As a cross-check, the version also appears at the bottom right of most admin screens. If it is at or above the number for its branch in the list above, the core is patched. If your site is run by an agency or host, send them this: “Is our WordPress core on the fixed release for CVE-2026-119977, and which version is it running?”

What to do if you’re on an older version

  • Take a backup first if your host does not take one automatically, then run the update from Dashboard, then Updates.
  • If your site supports automatic background updates, the release post says the update begins automatically. Check the Updates screen to confirm it has landed.
  • On managed hosting, the host may control core updates. Ask them for the version in writing and for a date if it has not happened.
  • After the update, look at the front of the site and the checkout or contact forms, since a core update occasionally exposes an old plugin that no longer works.

Reviewing the Users list for administrator accounts you do not recognise is good general practice after any serious flaw. It is not something the advisory reports.

Why one core update turns into a website problem

Core updates are the easy part of WordPress upkeep, and most of the time they happen without anyone noticing. The trouble is the sites where they do not: an old branch nobody moved, a host that holds back updates, a staging copy that was forgotten about. When a flaw is listed as exploited, the gap between “released” and “applied” is what matters.

That gap is a maintenance question. A WordPress site we build or take on has its core, plugins and themes reviewed on a schedule, and a support retainer covers following advisories like this one and chasing the host when a fix is late.

Not sure what else is out of date?

Core is one layer of several. If you want a person to look at the rest, ask for a free mini audit and we will email you a score, the three issues costing you most and three quick wins within two working days, or tell us about your site using the form below.

Written by

Alex

CEO

I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.