Guides

CISA Says a WordPress Core Flaw Is Being Exploited. Here’s What 7.1.4 Changed

Featured card: CISA flags a WordPress core flaw, CVE-2026-119977

Last updated 6 November 2026.

Short version first. If your WordPress site is on 7.1.4, or on the latest security build of an older branch (7.0.8, 6.9.11, 6.8.12 and so on), you have the fix for CVE-2026-119977. If it’s on anything from 4.7 through 7.1.3 without that build, update today. Most sites with automatic minor updates switched on already got it without anyone lifting a finger.

Why the noise this week? On 3 November the US Cybersecurity and Infrastructure Security Agency (CISA) added this WordPress core bug to its Known Exploited Vulnerabilities catalog. That list only takes bugs with evidence of real attacks. Wordfence told BleepingComputer it blocked 13,095 attacks aimed at it in a single 24-hour period.

Below: the bug in plain words, what 7.1.4 changed (we diffed the zips), and what to check.

What the flaw is

Here’s the official description from NVD, published 31 October:

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

Translated: when WordPress updates itself, it unpacks the new files into a temporary folder inside wp-content/upgrade/, which the web server can serve. Before 7.1.4 its name was predictable. An attacker who knew roughly when your site was updating could guess where the files would land and try to get code executed from there while the update ran.

That’s a timing attack, a race. The formal label is CWE-367, a “time-of-check time-of-use” race condition. It’s scored 8.1 (High) under CVSS 3.1, with the score coming from Wordfence. Note the attack complexity is rated High: the attacker has to hit a short window. But no login is needed, and if it works the impact is total. CISA’s own assessment says exploitation is “active”, the attack is not automatable, and the technical impact is “total”.

The bug was reported by Umut Bayram, a researcher at Picus Security according to BleepingComputer. The 7.1.4 release notes credit it as “A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window”.

Fixed versions by branch

WordPress 7.1.4 came out on 28 October 2026. As usual, the security fixes were backported to every branch still getting them, which currently means everything back to 4.7. This is what the wordpress.org version-check API offered on 6 November:

Your branch Fixed build
7.1 7.1.4
7.0 7.0.8
6.9 6.9.11
6.8 6.8.12
6.7 6.7.11
6.6 6.6.11
6.5 6.5.14
6.4 6.4.14
6.3 6.3.14
6.2 6.2.15
6.1 6.1.16
6.0 6.0.18
5.9 5.9.20
5.8 5.8.19
5.7 5.7.21
5.6 5.6.23
5.5 5.5.24
5.4 5.4.25
5.3 5.3.27

Older branches, all the way down to 4.7, get backports too. If you’re on one of those, check Dashboard › Updates for the build it offers.

7.1.4 wasn’t a one-bug release, by the way. It also fixed about a dozen other issues, mostly stored XSS bugs, plus a stored DoS in the Interactivity API and updated root certificates. Two of the XSS reports are credited to Anthropic. It fits the pattern we wrote about in October, when we counted 44 WordPress security fixes in 2026 against 2 in all of 2025.

What the patch actually changes

Release notes say what was fixed, not how. So we diffed the 7.1.3 and 7.1.4 zips. Three small upgrader changes matter here.

1. The working folder gets a random name

In wp-admin/includes/class-wp-upgrader.php, the unpack_package() method used to name its working folder after the package file, basically the zip’s file name. Easy to guess. 7.1.4 adds a new get_working_dir_name() method that tacks a dash and 16 random letters and digits onto the end, generated with wp_generate_password(16, false). You can’t guess that.

2. The upgrade folder can’t be listed

WordPress now writes an index.php (“Silence is golden”) into wp-content/upgrade/. On a server with directory listing turned on, an attacker could otherwise just open the folder in a browser and read the random name. The code comment says it plainly: “The upgrade directory is web-served. Keep it from being listed … so the name of the working directory created below cannot be discovered from a directory index.”

3. A stray wp-config.php never gets copied

In wp-admin/includes/update-core.php, the step that copies new core files into place now skips wp-config.php. The comment: “Never copy a wp-config.php, which could have been written to the working directory.” So a planted config file was clearly one abuse case the developers had in mind.

One more detail. unpack_package() is shared code. Plugin and theme updates go through it too, so the random folder name now applies to every package WordPress unpacks. The CVE itself, as written, is about full-package core upgrades. The hardening is just broader than the bug.

Who is actually exposed

On 6 November the wordpress.org stats showed 65.3% of reporting sites on the 7.1 branch, 6.7% on 7.0, 6.3% on 6.9, 5.0% on 6.8 and 2.5% on 6.7. Those are branch shares, though. WordPress.org doesn’t publish minor versions, so nobody outside can say how many sites are on 7.1.4 exactly. We won’t guess.

A few things narrow it down:

  • Auto-updates on? Minor automatic updates have been the default since WordPress 3.7. Those sites should already have the fix.
  • The window is the update itself. A vulnerable site is exposed while it updates. Once it’s on a fixed build, later updates use the random folder name.
  • Full packages are the named case. Looking at class-core-upgrader.php, core tries a partial package first, then a “no content” one, then the full one. Routine minor auto-updates normally use the smaller partial package when one’s available. That suggests manual reinstalls and major upgrades are where the full package comes in, but we’d treat that as a hint, not a guarantee.

The KEV timeline

Date (2026) What happened
28 Oct WordPress 7.1.4 released; backports to older branches follow
31 Oct CVE-2026-119977 published on NVD
3 Nov CISA adds it to the KEV catalog, forensic triage flag set
4 Nov BleepingComputer reports Wordfence blocked 13,095 attacks in 24 hours
6 Nov Patch deadline for US federal civilian agencies under BOD 26-04

That deadline is today. Three days is short.

Our data point: core is new to this list

We pulled CISA’s KEV JSON feed on 6 November and searched it for WordPress. Before July 2026 the catalog had zero entries for WordPress core. The only WordPress items were three plugins (File Manager, Duplicator and Social Warfare), all added on 3 November 2021, plus cPanel’s WP Squared product in April 2026.

Since July, four core entries:

  • CVE-2026-63030 and CVE-2026-60137, added 21 July. That’s the “wp2shell” chain fixed in 7.0.2. Public exploits showed up a day after the patch, and in September BleepingComputer reported a Chinese-speaking actor using it to steal more than 18,500 records.
  • CVE-2026-87902, added 25 September. Remote file inclusion via page-template resolution.
  • CVE-2026-119977, added 3 November. This one.

Four in under four months, after years of none. We don’t read that as core getting worse. Bugs are being found faster, and used faster. The gap between patch and attack is now very short.

What to check today

  1. Check your version. Dashboard › Updates, or wp core version if you use WP-CLI. Compare it with the fixed build for your branch in the table above.
  2. Make sure minor auto-updates aren’t off. Look for WP_AUTO_UPDATE_CORE set to false in wp-config.php (wp config get WP_AUTO_UPDATE_CORE will tell you), or a plugin or host setting that disables updates.
  3. Turn off directory listing. On Apache, add Options -Indexes. On nginx, autoindex is off unless someone turned it on. Worth a look either way.
  4. Look inside wp-content/upgrade/. Leftover folders or unexpected .php files there deserve a closer look.
  5. Check wp-config.php. Is there one somewhere you didn’t put it? Was yours changed recently when you didn’t change it?
  6. Check your admin users. Users › All Users, filtered by Administrator. Anyone new you don’t recognise is a red flag.
  7. If anything looks off, treat it as an incident. Updating closes the hole. It doesn’t remove something that already got in.

On managed hosting? Your host probably updated core for you. Still check the number. It takes ten seconds.

What we don’t know

We don’t know exactly how attackers get a file into that working folder during the update. The NVD text, the release note and the diff all point at the predictable path, and the wp-config.php change hints at one route. But nobody has published the full exploit chain, and we’re not going to fill the gap with guesses. We also can’t tell you how many live sites are still on a vulnerable build, because minor-version share isn’t public. The attack counts are snapshots too: one outlet reported 12,632, Wordfence’s quote said 13,095.

Next up: WordPress 7.2, planned for 8 December. We had an early look at what’s new in 7.2. If you’re also checking the server side this week, our post on the 21 October PHP security fixes covers that half.

Frequently asked questions

Is my WordPress site affected by CVE-2026-119977?

Yes, if it runs anything from 4.7 to 7.1.3 other than the newest security build for its branch. The fixed builds are 7.1.4, 7.0.8, 6.9.11 and so on down the branches. Sites with minor auto-updates switched on should already have it.

Can someone exploit this bug when my site isn’t updating?

According to the official description, the attack works during the upgrade window, when WordPress unpacks a full core package. Once you’re on a fixed version, the temporary folder gets a random name that can’t be guessed or listed.

I’ve updated. Do I need to do anything else?

Check that minor auto-updates stay on and that directory listing is off on your server. Then look in wp-content/upgrade/ for unexpected PHP files, check for a wp-config.php you didn’t put there, and review your admin users. If anything looks wrong, treat it as a possible break-in.