A WordPress vulnerability in the core software is being used in real attacks, and the fix is WordPress 7.1.4, released on 28 October 2026. If your business website runs WordPress and has not taken that update, or the patched release for its older branch, update it this week.
What happened with this WordPress vulnerability?
Three dates tell the story.
- 28 October 2026. WordPress published version 7.1.4, a security release, and recommended that site owners update immediately. One of the fixes closes a weakness in the WordPress upgrade process that can lead to remote code execution, which means an attacker running their own code on your server.
- 3 November 2026. The US Cybersecurity and Infrastructure Security Agency (CISA) added the flaw, tracked as CVE-2026-119977, to its Known Exploited Vulnerabilities catalogue. CISA describes it as a race condition in WordPress core and says the listing is based on evidence of active exploitation.
- 4 November 2026. BleepingComputer reported that the flaw is rated high severity and can be used by a remote attacker who has no privileges on the site. It also reported that security firm Wordfence had blocked 13,095 attacks aimed at it in 24 hours.
There is a calmer side to this. Patchstack's analysis of the release says the window for the attack is tiny and that it would not call the flaw practical to exploit. Patchstack also notes that the attack needs no account and that the window comes back every time a site updates. Both things are true. It is difficult to exploit, and people are trying anyway.
Who is affected?
WordPress sites that have not installed a patched release. WordPress says the fixes are also being sent back to older branches that still receive security updates, currently as far back as 4.7. The version 7.1.4 notes list 7.0.8, 6.9.11 and 6.8.12 among the releases that carry them. The same notes say versions 4.6 and earlier no longer receive security updates, so a site that old needs a full upgrade, not a patch.
Patchstack notes that sites with automatic background updates enabled receive 7.1.4 on their own. The sites to check are the ones where automatic updates have been switched off. Those sites only get the fix when someone installs it by hand.
What this means for your website
This flaw sits in WordPress core, not in a plugin or theme. A lean site with very few plugins is exposed in the same way as a large one until it is patched.
Remote code execution is among the most serious kinds of website flaw. Code that runs on your server can do whatever your website can do, which includes reading what is stored there and changing what visitors see.
For the web development industry, the lesson is about speed. Six days passed between the patch and CISA confirming attacks. A routine where updates are applied once a month, or whenever someone remembers, is too slow for a security release. Feature updates can wait for testing. Security releases need a same-week process, with a backup and a quick test plan ready before the day they are needed.
It is also a reminder that WordPress security is not only about plugins and passwords. For this flaw, Patchstack suggests a web server rule that denies web access to the folder WordPress uses during upgrades. That is a job for your developer or host, not a setting in the dashboard.
How do you check your WordPress version and update safely?
Work through this list today. On a simple site it is a short job.
- Log in to WordPress and open Dashboard, then Updates. The page shows your current version. If it says 7.1.4 or later, this flaw is fixed on your site.
- If you are on an older branch, the Updates page offers the patched release for that branch. To move to the WordPress latest version instead, plan it as a tested upgrade.
- Take a full backup of files and database before you update. Check that you know how to restore it.
- Run the update. On a store or a complex site, update a staging copy first.
- Test what earns you money: enquiry forms, checkout, bookings and login.
- Confirm that automatic updates for security releases are switched on. If they were turned off, find out who did it and why.
- If the site sat unpatched for a while, review your admin users. An account nobody recognises is a reason to get help straight away.
- Ask your host or developer whether the server blocks web access to the WordPress upgrade folder.
Is WordPress still safe for a business website?
Yes, when someone is responsible for it. WordPress had a fix out six days before CISA confirmed attacks, and sites with background updates switched on should have received it on their own. The risk sits with websites that nobody is watching.
If you cannot name the person who applies your security updates, that is the real finding here. We made the same point after the Coles cyber attack: know who looks after your logins, updates and backups before the day you need them.
How Web Mage can help
We look after WordPress, WooCommerce and Shopify sites on monthly care plans. Updates are tested on a staging copy before they go live, backups are kept off-site, and security releases are applied once they pass that test. See what is included in our website maintenance plans, or read how we approach WordPress development when a site needs more than a patch.
Not sure which version you are on, or who is meant to be updating it? Contact us with your site address and we will tell you where you stand.


![6 Best Web Design Agencies in Brisbane [2026]: featured image](/wp-content/uploads/2026/11/brisbane-web-design-agencies-featured-webmage.webp)
