ServicesManaged IT servicesMicrosoft 365CybersecurityCloud & projectsManaged IntelligenceWhy MSP LogicHealth checkSecurityReviewsBlogsSecurity NewsAboutBook
SECURITY NEWS

WordPress upgrade flaw exploited: update now

A race condition in the WordPress Core upgrade process can let attackers run code on your site during updates. CISA has added it to the known exploited list — here's who is affected and what to do this week.

Source: BleepingComputer – CISA flags WordPress RCE flaw as actively exploited in attacks

If your business website runs on WordPress, this one is worth acting on this week. A flaw in how WordPress Core handles upgrades can let an attacker run code on the site while an update is in progress, and security agencies say it is already being used in real attacks.

What happened

BleepingComputer reported that the US Cybersecurity and Infrastructure Security Agency (CISA) has added a WordPress Core remote code execution flaw, tracked as CVE-2026-119977, to its Known Exploited Vulnerabilities catalog. The issue is a time-of-check to time-of-use (TOCTOU) race condition in the WordPress upgrade process. During a full-package core upgrade, WordPress stages files under predictable, web-accessible paths in wp-content/upgrade. An unauthenticated attacker who wins the race can plant malicious code before the upgrade finishes locking things down.

WordPress released version 7.1.4 on 28 October 2026 to fix it, with backported security releases for older branches. As quoted by BleepingComputer, the WordPress security team said: "A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window… update your sites immediately." CISA urged private-sector organisations to patch, and set a Friday deadline for US federal civilian agencies under Binding Operational Directive 26-04.

Wordfence told BleepingComputer it had blocked 13,095 attacks targeting this vulnerability in the past 24 hours, according to its weekend advisory update. That volume shows scanners are already hunting for unpatched sites.

Who is affected

According to the WordPress and Wordfence advisories summarised by BleepingComputer, the flaw affects WordPress Core versions 4.7 through 7.1.3. Sites already on 7.1.4, or on the matching backported security release for their branch, are patched. Wordfence's write-up lists the fixed versions for each supported line.

You are most exposed if your site still allows automatic or manual full-package core upgrades over the public web, and if the staging directory under wp-content/upgrade is reachable from the internet during that window. Managed hosts that apply core updates for you may already have shipped the fix; self-hosted and cheap shared-hosting sites are often left behind.

Official details are in the WordPress 7.1.4 documentation and the WordPress 7.1.4 release post. Wordfence also published a technical deep dive on the race condition.

Why it matters for Australian businesses

A large share of Australian small and medium business websites run on WordPress — marketing sites, booking forms, member portals and online shops. Remote code execution on the CMS means an attacker can deface the site, steal customer data, plant malware that hits your visitors, or use the server as a foothold into email and file systems that share the same hosting account.

This is not an isolated WordPress scare. BleepingComputer notes an earlier wp2shell exploit chain in July and a Chinese-speaking actor campaign in September that stole more than 18,500 records from small businesses and government targets — further reason to treat WordPress core and plugin patching as urgent, not optional.

The Australian Cyber Security Centre has previously warned about large-scale exploitation campaigns against website CMS platforms, including WordPress. Patching internet-facing applications sits at the heart of the Essential Eight guidance on cyber.gov.au. Leaving a public WordPress site on 7.1.3 or older while this CVE is in the wild is exactly the kind of gap that guidance is meant to close.

What to do now

  1. Check your WordPress version. In wp-admin, open Dashboard → Updates, or look at the version in the footer. Anything from 4.7 through 7.1.3 needs the matching security release.
  2. Update Core to 7.1.4 (or your branch's patched release). Take a full backup of files and the database first, then run the update from the dashboard or ask your host to apply it. Confirm the site still loads and that login, forms and checkout still work.
  3. Update plugins and themes in the same window. Out-of-date plugins are a common second path in after a core compromise. Remove anything you no longer use.
  4. Review who can trigger upgrades. Limit wp-admin access to named accounts with strong MFA, and prefer host-managed or staged updates over leaving auto-update running unattended on a live production site during an active exploit window.
  5. Watch for odd files under wp-content/upgrade. Ask whoever manages the site to check that directory and recent web server logs for unexpected PHP files or traffic spikes around upgrade times since late October.
  6. Put WordPress on a monthly patch schedule. Core, plugins and themes should be checked at least monthly — more often when a CVE is listed as actively exploited.

How MSP Logic can help

If you're not sure which WordPress version your site runs, whether the upgrade path is exposed or how to apply 7.1.4 without breaking the site, we can check it for you, take a backup, apply the security update and confirm forms and logins still work. Ongoing CMS and plugin patching sits under our cybersecurity services, and we can fold website care into broader managed IT services so issues like this are handled before attackers find them.

Want a second pair of eyes on your WordPress site? Get in touch and we'll take a look.

Source: BleepingComputer – CISA flags WordPress RCE flaw as actively exploited in attacks. This article is MSP Logic's own summary and advice; read the original report for full details.

NEED A HAND?

Want us to check this for you?

Book a free, no-obligation IT review and we'll show you where you stand and what to fix first.