WordPress Core Flaw CVE-2026-119977: Update Now
Published October 31, 2026 · Last updated October 31, 2026
The short version: CVE-2026-119977 is a high-severity security flaw in WordPress Core. The National Vulnerability Database (NVD) published it on October 31, 2026, and the score it lists is 8.1 out of 10. When FraudMeNot checked on October 31, 2026, CISA had not added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-119977
The record was filed by wordfence.com. In its own words: "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."
Why WordPress Core admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on wordfence.com rated CVE-2026-119977 8.1 (High) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping WordPress Core running is high. Scoring string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected WordPress Core releases
According to the record, these releases are vulnerable:
- 4.7.0 through 4.7.38
- 4.8.0 through 4.8.33
- 4.9.0 through 4.9.34
- 5.0.0 through 5.0.30
- 5.1.0 through 5.1.27
- 5.2.0 through 5.2.29
- 5.3.0 through 5.3.26
- 5.4.0 through 5.4.24
The type of bug behind CVE-2026-119977
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition. MITRE describes this class of bug as follows: "The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check."
Vendor remediation for CVE-2026-119977
The vendor advisory remediation for operators of WordPress Core, quoted for this page, is: "Update WordPress to 7.1.4 or newer, released in October 2026 by the WordPress project (wordpress.org/news/2026/10/wordpress-7-1-4/). The flaw affects every version from 4.7 through 7.1.3. Site owners and hosting providers should confirm automatic background updates are on, or update from Dashboard, Updates, and avoid leaving a manual core upgrade half-finished."
What to do about it
- Update now: Update WordPress to 7.1.4 or newer, released in October 2026 by the WordPress project (wordpress.org/news/2026/10/wordpress-7-1-4/). The flaw affects every version from 4.7 through 7.1.3. Site owners and hosting providers should confirm automatic background updates are on, or update from Dashboard, Updates, and avoid leaving a manual core upgrade half-finished.
- Who should act: IT teams, managed service providers, and developers who run or ship WordPress Core. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from WordPress (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 31, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-119977. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-119977 record details from CISA and NVD
- Attack complexity for CVE-2026-119977: high
- CVE-2026-119977 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-119977: exploitability 2.2, impact 5.9.
- Who mapped the weakness type: the address listed on wordfence.com (Primary)
- References in the NVD record: 8.
Dates to know
- October 31, 2026: NVD publishes CVE-2026-119977.
- October 31, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-119977 is not listed.
- October 31, 2026: most recent NVD update (record status: Received).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L37
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L34
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545
- wordpress.org/news/2026/10/wordpress-7-1-4
- www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?sou
Sources
- NVD: CVE-2026-119977
- CVE.org: CVE-2026-119977
- WordPress advisory
- WordPress advisory
- WordPress advisory
- MITRE CWE-367
General education only, not security advice. Facts checked against the sources above on the date shown.