WordPress Core Flaw Exploited During Updates: Make Sure You're on 7.1.4 (CVE-2026-119977)
WordPress 4.7 through 7.1.3 can let an unauthenticated attacker run code on your web server while a core update is in progress. CISA says it is being exploited. Update to WordPress 7.1.4, or to the patched release for your branch, and check that automatic updates are working.
What happened
On 28 October 2026, WordPress released version 7.1.4, a security release fixing more than a dozen issues. The most serious is CVE-2026-119977, which WordPress describes as a weakness in the upgrade process that can lead to remote code execution during the upgrade window.
According to the CVE record and CISA, full-package core upgrades use temporary staging paths that are predictable and reachable from the web. An attacker who doesn't need to log in can take advantage of that brief window to run code on the server. On 3 November 2026, CISA added the flaw to its Known Exploited Vulnerabilities catalog, meaning it has evidence of real attacks.
Code running on your web server can deface the site, add spam or malicious redirects, steal form submissions, or give an attacker a foothold on the hosting account.
Who is affected
Any self-hosted WordPress site running version 4.7 through 7.1.3. That covers almost every WordPress site that hasn't installed 7.1.4 or a patched backport.
The flaw is in WordPress itself, not in a plugin or theme, so even a site with a minimal setup is affected. Sites on managed WordPress hosting are often updated by the host, but it's worth confirming rather than assuming.
Is it being exploited?
Yes. CISA lists CVE-2026-119977 as known exploited. CISA has not said whether ransomware groups are using it.
When to get outside help
Many small business websites were built by an agency or freelancer and are now looked after by no one. If you can't say who updates your site, or you're running a version older than 7.1, a vulnerability scanning service can check your public-facing sites and tell you what's out of date. If the site is behaving oddly, for example unfamiliar admin users, new files, or visitors being redirected elsewhere, get help cleaning it up rather than just updating it.
What to do
- Update to WordPress 7.1.4 or later. WordPress says to download it from WordPress.org, or go to Dashboard > Updates and click "Update Now". Sites with automatic background updates will update themselves.
- If you're on an older branch, WordPress is backporting the security fixes to every branch back to 4.7. Install the latest release for your branch, or better, move to the current version. WordPress notes that only the most recent version is actively supported.
- Check that automatic updates are actually running. Confirm the site reports 7.1.4 or later rather than assuming it updated.
Related guides
Sources
- WordPress 7.1.4 (WordPress.org)
- Known Exploited Vulnerabilities Catalog: CVE-2026-119977 (CISA)
- CVE-2026-119977 (CVE Program (Wordfence as CNA))
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
