Update WordPressto 7.1.4 now.
A flaw in every WordPress from 4.7 to 7.1.3 lets a stranger run code on the server, and so far only 7.1.4 fixes it.
- No loginneeded to run code on the server
- 4.7 to 7.1.3every version open until it is updated
- 1 in 3WordPress sites we checked on 3 Nov were still open
Who this is for
Any site built on WordPress, including shops that run WooCommerce. It does not affect Wix, Squarespace, Shopify or sites built by hand. If you are not sure what your site runs on, or which version, the free Mendbird check will tell you.
What changed
WordPress released version 7.1.4 on 28 October to fix twelve security flaws, and asked everyone to update straight away. The most serious, CVE-2026-119977, is in the way WordPress updates itself.
On 3 November the US cyber security agency, CISA, added it to its list of known exploited vulnerabilities. That list only holds flaws it has evidence attackers are using. US government departments had until 6 November to fix it.
How the attack works
When WordPress installs a full new version of itself, it first unpacks the new files into a working folder on the server. The flaw is that the folder's address is easy to guess and can be reached from the web. For the moments the update takes, a stranger who asks for the right file at the right time can make the server run their own code, without logging in.
The timing makes the attack harder to pull off, which is why it is scored 8.1 out of 10 rather than higher. But once it works, the stranger can do anything the site can: read the database, add admin accounts or change the pages visitors see.
Why automatic updates may not have covered you
Most WordPress sites install small updates on their own, but only within their own version line. A site on 6.8 moves from 6.8.11 to 6.8.12, never to 7.1.
WordPress has said it will bring the fix to every older line back to 4.7, but as of 10 November it has not released any of them. So 7.0.8, 6.9.11, 6.8.12 and the latest version on every other line are all still open, even on a site that updates itself perfectly.
When we checked 679 local business websites on 3 November, 188 showed which WordPress version they ran. 61 of them, about one in three, were on a version with this flaw. Half of those were fully up to date on an older line, and another 12 were just one update behind on 7.1.
What to do now
Check the version. In the WordPress dashboard, open Updates. Anything below 7.1.4 is open.
On 7.1, update now. Moving from 7.1.3 to 7.1.4 is a small update and should not change anything else on the site.
On an older line, there are two choices. Move up to 7.1.4, which is a bigger step: take a backup first and check your plugins and theme work with it. Or wait for WordPress to release the fix for your line, which your site will then install on its own. Waiting leaves it open until then, so if the site takes payments or personal details, moving up is the safer choice.
Did anyone get in first? Ask whoever looks after the site to look for admin accounts nobody remembers making and files changed around the time of an update. Many hosts will scan for this if asked.
Ask your developer“Which WordPress version is our site on, and can you get it to 7.1.4 this week? If that is a big jump for us, what would it take, and have you checked we were not broken into already?”
How Mendbird helps
The free Mendbird check reads the WordPress version from the outside whenever the site shows it, and marks any version from 4.7 to 7.1.3 as Dangerous, on every version line. On a Watch plan it checks every morning and emails you the day something serious is new, so you would also hear when your line gets its fix.