CVE-2026-119977: WordPress Core, is it exploitable where you run it
Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions
What the flaw is
WordPress core unpacks the update package into a working folder under wp-content/upgrade during a full-package core upgrade. In versions before the fix, that folder was named after the package file, so its name could be predicted, and the upgrade folder was served by the web server with no index file. NVD describes it as remote code execution by unauthenticated attackers through predictable, web-accessible staging paths during the upgrade window. The folder naming comes from a comparison of the 7.1.3 and 7.1.4 code. KEV classes it as a time-of-check time-of-use race condition (CWE-367).
The window is short and exists only while an upgrade is running, so NVD's CNA score (CVSS 3.1 of 8.1) rates attack complexity High. Sites that accept automatic background updates open the window on their own without an admin present. Because the working folder is created by the updater code already installed, the upgrade that installs the fix still runs the old logic. In version 7.1.4 the folder gets a random 16 character suffix, the upgrade folder gets an index.php so it cannot be listed, and the updater refuses to copy a wp-config.php from the working folder.
Are you exposed: each condition and how to check it
| Condition for exposure | How to check it on your system |
|---|---|
| Version: the WordPress core in use is below the first fixed release for its branch. | Run wp core version (WP-CLI), or grep wp_version wp-includes/version.php, or open the dashboard under Dashboard > Updates. Compare with the first fixed release for your branch in the versions table: 7.1.4, 7.0.8, 6.9.11 and so on down to 4.7.39. A fixed backport such as 6.9.11 is not affected even though it is numbered below 7.1.4. |
| A core upgrade runs on this site: manual, WP-CLI or automatic. | Check whether automatic core updates are on: Dashboard > Updates states that the site is kept updated automatically, and wp config get WP_AUTO_UPDATE_CORE shows an override in wp-config.php. Look at past runs in the web server log for admin update requests and in wp-content/upgrade for leftover folders. |
| The staging area wp-content/upgrade is reachable over HTTP. | From a host outside your network, run curl -sI https://your-site.example/wp-content/upgrade/ and read the status. A 200 or a directory listing means reachable. 403 or 404 means the web server already blocks it, which removes this condition. On a patched site the folder also holds an index.php. |
| The unpacked working folder has a predictable name (the unfixed behavior). | During or after an upgrade, run ls -la wp-content/upgrade/. A folder named after the package, such as wordpress- |
Affected and fixed versions
| Branch | Affected | First fixed release |
|---|---|---|
| 7.1 | 7.1.0 through 7.1.3 | 7.1.4 |
| 7.0 | 7.0.0 through 7.0.7 | 7.0.8 |
| 6.9 | 6.9.0 through 6.9.10 | 6.9.11 |
| 6.8 | 6.8.0 through 6.8.11 | 6.8.12 |
| 6.7 | 6.7.0 through 6.7.10 | 6.7.11 |
| 6.6 | 6.6.0 through 6.6.10 | 6.6.11 |
| 6.5 | 6.5.0 through 6.5.13 | 6.5.14 |
| 6.4 | 6.4.0 through 6.4.13 | 6.4.14 |
| 6.3 | 6.3.0 through 6.3.13 | 6.3.14 |
| 6.2 | 6.2.0 through 6.2.14 | 6.2.15 |
| 6.1 | 6.1.0 through 6.1.15 | 6.1.16 |
| 6.0 | 6.0.0 through 6.0.17 | 6.0.18 |
| 5.9 | 5.9.0 through 5.9.19 | 5.9.20 |
| 5.8 | 5.8.0 through 5.8.18 | 5.8.19 |
| 5.7 | 5.7.0 through 5.7.20 | 5.7.21 |
| 5.6 | 5.6.0 through 5.6.22 | 5.6.23 |
| 5.5 | 5.5.0 through 5.5.23 | 5.5.24 |
| 5.4 | 5.4.0 through 5.4.24 | 5.4.25 |
| 5.3 | 5.3.0 through 5.3.26 | 5.3.27 |
| 5.2 | 5.2.0 through 5.2.29 | 5.2.30 |
| 5.1 | 5.1.0 through 5.1.27 | 5.1.28 |
| 5.0 | 5.0.0 through 5.0.30 | 5.0.31 |
| 4.9 | 4.9.0 through 4.9.34 | 4.9.35 |
| 4.8 | 4.8.0 through 4.8.33 | 4.8.34 |
| 4.7 | 4.7.0 through 4.7.38 | 4.7.39 |
If the fix cannot go in yet
- Update to the fixed release for your branch, preferably the newest release of your branch (7.1.5 for the 7.1 branch, released 18 Nov 2026). Cost: a short upgrade window, which is the exposure itself. On a public site, put the block from the next item in place first, then run the update.
- WordPress.org names no workaround in the 7.1.4 release note. The exposure-reducing step that follows from the code change is to deny web access to wp-content/upgrade. For nginx add location ^~ /wp-content/upgrade/ { deny all; } and for Apache add a Require all denied rule for that directory, then reload the web server. Cost: none for visitors, since the folder only holds update files. The rule is derived from the 7.1.4 change, which adds an index.php to that folder, not from a vendor statement. Before the update begins, the block must already be in place, because the vulnerable updater that installs the fix still creates the predictable folder.
- Automatic background updates start the window with nobody watching. The release note says sites that support them begin the 7.1.4 update on their own. With the block in place they are safe to leave on. Holding a site on an old release to avoid the window keeps it exposed to every later upgrade.
- After any upgrade on an unpatched site, review the site for unexpected files (see detection). WordPress.org gives no further workaround.
What to look for
- Version check: wp core version, or grep wp_version wp-includes/version.php, compared with the versions table.
- After each upgrade on a site that ran code before 7.1.4: list wp-content/upgrade/ and remove stale folders. In the unfixed code the working folder is named after the package, so look for a leftover folder there, or any .php file you did not put there.
- Check core files against the official checksums: wp core verify-checksums reports modified and unknown files in the WordPress root and wp-includes. Compare wp-config.php with your last known good copy, because the 7.1.4 updater refuses to copy a wp-config.php from its working folder. Look for new admin users (wp user list --role=administrator) and new files under wp-content/uploads and wp-content/plugins.
- In web server logs, look at requests for /wp-content/upgrade/ paths made in the minutes around a core upgrade. A 200 from a path under that folder that is not an update file is suspect.
- WordPress.org, Wordfence and CISA publish no indicator addresses or payload strings for this flaw. CISA marks forensic triage as required in KEV.
The earliest dated mark of exploitation is CISA's, on 3 Nov 2026, 6 days after disclosure; exploitation may have begun earlier.
Exploitation reported so far
CISA added the CVE to KEV on 3 Nov 2026, three days after NVD published it and six days after the fix, and its SSVC entry in NVD records exploitation as active and not automatable. KEV lists ransomware campaign use as Unknown.
CISA publishes no first exploitation date, attacker or indicators for this CVE. The 3 Nov 2026 KEV listing is the earliest dated public report of exploitation, so the days from fix to exploitation on this page measure the gap to the listing, not an observed attack.
Why runtime reachability settles it
Exposure needs an upgrade running at that moment and an upgrade folder the attacker can reach, which are runtime conditions. Checking whether the staging path answers over HTTP and whether automatic updates are on tells you more than the version number does. The fixed version still ends the question. See runtime reachability for what the method proves and misses.
Related pages
Sources
- CVE-2026-119977: NVD record, read 19 Nov 2026
- CVE-2026-119977: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
- CVE-2026-119977: vendor advisory (WordPress 7.1.4 security release note), read 19 Nov 2026
- CVE-2026-119977: WordPress HelpHub page for version 7.1.4, read 19 Nov 2026
- CVE-2026-119977: WordPress.org releases page (release dates of backports), read 19 Nov 2026
- CVE-2026-119977: WordPress core source, 7.1.3 tag, class-wp-upgrader.php (before the fix), read 19 Nov 2026
- CVE-2026-119977: WordPress core source, 7.1.4 tag, class-wp-upgrader.php (after the fix), read 19 Nov 2026
- CVE-2026-119977: WordPress core source, 7.1.3 tag, update-core.php, read 19 Nov 2026
- CVE-2026-119977: WordPress core source, 7.1.4 tag, update-core.php, read 19 Nov 2026
- CVE-2026-119977: WordPress.org version check API (current releases per branch), read 19 Nov 2026
Last reviewed 19 Nov 2026.