Most security advice ends with "update now". This time, the update is part of the problem. A flaw in WordPress core, tracked as CVE-2026-119977, can let an attacker run code on your server during the few seconds an older WordPress site is installing a full core update. They don't need an account on the site. WordPress fixed it on 28 Oct 2026, and attempts to exploit it have since been reported. On 3 Nov, it was added to a US government list of vulnerabilities known to be exploited in real attacks.
In short: if your site already runs WordPress 7.1.4, or the fixed release for its branch such as 7.0.8, this flaw is closed for future updates. If it runs an older, unpatched version, don't just click Update Now. Back up, test on a copy, protect the update window, update, then confirm the version and check for signs of compromise.
What the flaw is, in plain English
When WordPress updates itself with a full package, it unpacks the new files into a temporary folder inside your site before copying them into place. Before the fix, that folder had a name anyone could work out in advance, and it could be reached from the web. The official description calls the cause "predictable, web-accessible staging paths used during full-package core upgrades".
In practice, an attacker can keep sending requests to that predictable address and wait. If one lands while the update is running, they can take over the temporary copy and run code on the server. The window is short, but the requests are cheap, so patience pays.
WordPress 7.1.4 fixes this by giving the temporary folder a random name, among other changes. The same fix was released for older branches back to 4.7, for example 7.0.8, 6.9.11, 6.8.12 and 4.7.39. WordPress 4.6 and earlier get no security updates at all.
Why the first update is the risky moment
This is the part that catches people out. The fix lives inside the new version, but the update is carried out by the old version already on your server. So the first update from an unpatched release to a fixed one still uses the old, predictable folder.
According to the researchers who analysed it, the main exposure right now is a site on an unpatched release older than 7.1 clicking Update Now, because that jump uses a full package. Sites on 7.1 to 7.1.3 currently get a smaller package that doesn't trigger the attack, but they stay exposed on a later update until 7.1.4 is installed. Sites that already completed an automatic security update to a fixed release are protected from here on.
Don't assume automatic updates did their job. A site restored from an old backup, or one where an update failed quietly, can still be on a vulnerable version.
How to update an old WordPress site safely
Treat the update as a small project, not a click.
wp-content/upgrade/ folder while the update runs, or to update by replacing the core files manually from the official package instead of using Update Now.wp core version on the server. Then compare the core files with the official copies using wp core verify-checksums./wp-content/upgrade/, especially repeated POST requests around the time of an update. Check for unexpected changes to wp-config.php, new administrator accounts, plugins nobody installed, and connections from the server to a database you don't recognise.If you find anything suspicious, take the site offline, keep the logs, restore from a clean backup, and change the database password, the WordPress security keys, admin sessions and any API keys the site uses.
Update, 5 Nov: check PHP too, and confirm the update finished
Updating WordPress core doesn't update PHP, the server software WordPress runs on. On 21 Oct the PHP project fixed two separate critical flaws, CVE-2026-109618 and CVE-2026-109619, that can let an attacker run code without logging in. In Tools, then Site Health, then Info, check that your PHP version is at least 8.5.12, 8.4.27, 8.3.36 or 8.2.35 for its branch, or that your host confirms the fix is included. PHP 8.1 and older no longer get updates from the PHP project. Then check your last WordPress update actually finished: confirm the version in Dashboard, then Updates, and run wp core verify-checksums. More in our PHP security update guide. Source: PHP security advisory, 21 Oct 2026.
Update, 6 Nov: US federal agencies had a patch deadline today
On 4 Nov, reports confirmed that attackers are actively exploiting CVE-2026-119977, and that US federal civilian agencies were required to secure their systems by Friday 6 Nov. The same notice urged private-sector defenders to prioritise the fix. The flaw is already covered above: it sits in the full-package core upgrade window and is fixed in WordPress 7.1.4 and the backports for older branches. If you have not yet confirmed Dashboard shows a fixed release, do that now, then check that the update finished and review logs for unusual requests under /wp-content/upgrade/. Source: BleepingComputer, 4 Nov 2026.
Why sites nobody maintains should be modernised
The sites most exposed to this kind of flaw are the ones nobody is watching: an old marketing site, a microsite from a past campaign, a marketplace built years ago by a team that has since moved on. They stay on old versions because updating feels risky, and over time that becomes the bigger risk.
WordPress only actively supports its latest version. Every year a site sits on an old branch, the jump gets bigger, the plugins get older, and an urgent update like this one gets harder. That's the real cost of technical debt: not one big failure, but every small change getting slower and riskier.
Modernising doesn't have to mean a rebuild. Often it means getting the site onto a supported version, removing plugins nobody uses, adding a staging copy and a weekly update routine, and giving someone clear ownership. Where the platform has outgrown WordPress, it can mean moving the important parts onto something easier to maintain. We've done this kind of work on a long-running niche marketplace we've supported for two years. Read the case study.
Plugins need the same routine. Our post on the Gravity Forms vulnerability covers a recent example.
FAQ
Which WordPress versions fix CVE-2026-119977?
WordPress 7.1.4, plus the fixed security releases for older branches back to 4.7, such as 7.0.8, 6.9.11 and 4.7.39. WordPress 4.6 and earlier get no security updates.
Is my site at risk if automatic updates are on?
If the automatic security update completed and your site now runs a fixed release, later updates are protected. Check the version number anyway, because failed updates and restored backups are common.
Why is clicking Update Now risky on an old site?
The update is carried out by the old code already on your server. On an unpatched site, a full update package is unpacked into a predictable folder, and that is the moment an attacker can use.
Does the attacker need a login?
No. The flaw can be exploited without an account on the site, but only during the short window while a full core update is running.
How do I know if my site was attacked?
Look for requests to /wp-content/upgrade/ in your server logs, changes to wp-config.php, unknown administrator accounts or plugins, and core files that don't match the official checksums. If you find any, restore from a clean backup and change your passwords and keys.
What if my site runs WordPress 4.6 or earlier?
There is no security fix for those versions. The safe route is a planned migration to a supported version or a new platform, tested on a copy first.
Need a hand with an old WordPress site?
Book a free consult and we'll look at what your site runs on, what a safe update path looks like, and what it would take to keep it maintained. We can run your whole tech area as your tech team, or work alongside your developers as a senior team. You keep ownership of your code, data and accounts. See our services.
WhatsApp +971 585692165 · contact@souzalabs.io
Sources: WordPress 7.1.4 release notes and Version 7.1.4 on HelpHub, 28 Oct 2026. Checked on 4 Nov 2026.