CISA says a WordPress core flaw (CVE-2026-119977) is being exploited during upgrades: update to the 7.1.4 security release
CISA added CVE-2026-119977, a race condition in WordPress core, to its Known Exploited Vulnerabilities list on 3 Nov 2026. It can let an unauthenticated attacker run code on the server during the upgrade window. WordPress fixed it in the 7.1.4 security release on 28 Oct, with fixes rolling out to older branches. What to update, what to check, and what we could not confirm.
Updated 5 Nov 2026: see what changedHow urgent
Act now
Who is affected
Sites running WordPress core that have not installed the 7.1.4 security release (or the matching fix for their branch). The problem is in the way full-package core upgrades stage their files, so it matters most for sites that upgrade core. Sites with automatic background updates should have received the fix
What to do
Update WordPress to 7.1.4 now (Dashboard, Updates, Update Now) or confirm automatic updates ran, and for older branches use the fix your branch has been offered. Then check whether you upgraded core in the last weeks: look for files you did not add, unknown admin users and changed core files, and restore from a clean backup if something looks wrong
Published 4 Nov 2026 · Sources last checked 5 Nov 2026No. 45 / 87
Updates, follow-ups and corrections
- Update · 5 Nov 2026. More detail from a report that cites Wordfence's advisory (we could not open Wordfence's own page): WordPress 4.7 through 7.1.3 are affected, attackers were probing within hours of the 28 Oct release, and Wordfence reported no confirmed compromises. Attack counts differ between reports, so we do not quote one. Hosts can also block web access to the upgrade folder.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 3 November 2026, CISA added CVE-2026-119977 to its Known Exploited VulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary (KEV) catalog, which means it considers the flaw to be exploited in real attacks. The entry describes a time-of-check time-of-use race condition in WordPress core: during a full-package core upgrade, the files are staged in predictable, web-accessible locations, and an unauthenticated attacker could use that window to run code on the server.
What is fixed
WordPress published the 7.1.4 security release on 28 October 2026 (updated 29 October). Among the fixes, it lists a weakness in the upgrade process that could allow remote code executionRCE (remote code execution) A flaw that lets an attacker run their own code on your server or device from a distance. Tap again to open the glossary during the upgrade window, plus a series of stored cross-site scripting fixes. The post says the fixes are backported to all branches still eligible for security fixes (currently back to 4.7) and that those backports are rolling out as they are ready. Sites with automatic background updates update on their own.
What to do
Our advice, based on the WordPress.org post and the CISA entry:
- Update now. In the dashboard go to Updates and click Update Now, or download 7.1.4 from WordPress.org. If you stay on an older branch, install the fix your branch is offered and check the version afterward.
- Check that automatic updates really ran. The version number in the dashboard footer or the Updates page should match the fixed release.
- Look for signs of a break-in if you upgraded core recently. Check for files you did not add (especially PHP files in unexpected folders), new administrator users, changed core files, and unusual requests in your server logs around the time of the upgrade. If anything looks wrong, restore from a clean backupBackup A copy of your data kept apart from the original, so you can recover it if something is lost, broken or locked. Tap again to open the glossary and change your passwords and keys.
- Reduce the window. Upgrade at a quiet time and do not leave half-finished upgrades lying around.
CISA gave federal agencies until 6 November 2026 and asks for a forensic triage as part of the response. That requirement is for agencies, but the idea is useful for anyone: do not only patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary, also check.
Update, 5 November
A report that cites Wordfence's advisory (we could not open Wordfence's page, so this is second-hand) adds: the flaw works by requesting the staged installer under wp-content/upgrade/ while a full-package core update is being unpacked, a window of seconds in Wordfence's tests. WordPress 4.7 through 7.1.3 are affected, and the fix is in 7.1.4 and in backports down to 4.7.39. Attackers were probing within hours of the 28 October release, and Wordfence reported no confirmed compromises. Reported counts of blocked attacks differ between sources and time windows, so we do not quote one.
If you cannot update right away, or you run many sites, a host-level rule that denies web access to wp-content/upgrade/ (and turns off directory listing) is reported as a way to block the attack; a WordPress-level firewallFirewall A filter that decides which network traffic may reach a device or service and which is blocked. Tap again to open the glossary cannot, because the staged copy runs its own files. This is a stop-gap, not a replacement for updating. Wordfence's free firewall rule is reported to arrive on 27 November.
What we could not confirm
We read the CISA catalog entry and the WordPress.org release post. We could not open The Hacker News article or the Wordfence advisory, so we do not know who is behind the attacks, how many sites were hit, or the exact range of affected versions beyond what the WordPress post says about backports. CISA lists known use in ransomwareRansomware Malicious software that locks your files or systems, and often steals a copy first, then demands payment. Tap again to open the glossary campaigns as unknown. We did not test the exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary and we are not publishing technical details beyond the vendor description.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- CISA: Known Exploited Vulnerabilities catalog, CVE-2026-119977 (added 3 Nov 2026, due date 6 Nov, read directly in the catalog data) (opens in a new tab)
- WordPress.org: WordPress 7.1.4 security release (28 Oct 2026, updated 29 Oct, read directly) (opens in a new tab)
- The Hacker News: CISA confirms hackers exploiting WordPress core flaw during software upgrades (4 Nov 2026; headline only, not opened) (opens in a new tab)
- Web Hosting Today: report citing Wordfence and Patchstack on the WordPress update flaw (2 Nov 2026, read directly; Wordfence's own advisory could not be opened) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.