CVE-2026-119977
WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability
Description
CVE-2026-119977 is a remote code execution vulnerability in WordPress Core versions 4.7 through 7.1.3, caused by a time-of-check time-of-use (TOCTOU) race condition in the full-package core upgrade process. During such an upgrade, WordPress stages files under predictable, web-accessible paths, and an unauthenticated attacker who requests them inside the upgrade window can execute code on the server. Successful exploitation of CVE-2026-119977 gives the attacker full control over the WordPress installation and its data. CISA has added the vulnerability to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation, with a remediation deadline of 2026-11-06.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| wordpress | wordpress | >= 4.7, < 4.7.39; >= 4.8, < 4.8.34; >= 4.9, < 4.9.35; >= 5.0, < 5.0.31; >= 5.1, < 5.1.28; >= 5.2, < 5.2.30; >= 5.3, < 5.3.27; >= 5.4, < 5.4.25; >= 5.5, < 5.5.24; >= 5.6, < 5.6.23; >= 5.7, < 5.7.21; >= 5.8, < 5.8.19; >= 5.9, < 5.9.20; >= 6.0, < 6.0.18; >= 6.1, < 6.1.16; >= 6.2, < 6.2.15; >= 6.3, < 6.3.14; >= 6.4, < 6.4.14; >= 6.5, < 6.5.14; >= 6.6, < 6.6.11; >= 6.7, < 6.7.11; >= 6.8, < 6.8.12; >= 6.9, < 6.9.11; >= 7.0, < 7.0.8; >= 7.1, < 7.1.4 |
References
- https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162(Product)
- https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378(Product)
- https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549(Product)
- https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282(Product)
- https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346(Patch)
- https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545(Patch)
- https://wordpress.org/news/2026/10/wordpress-7-1-4/(Release Notes)
- https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977(US Government Resource)
- https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution(Third Party Advisory)
Weakness Type
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
In CVE-2026-119977, WordPress Core assumes its staged upgrade files are safe during the upgrade, but between staging and completion they sit at predictable, web-reachable locations. An attacker who hits that window can act on the files before the upgrade finishes.
Learn more: CWE-367 — Time-of-check Time-of-use (TOCTOU) Race Condition
Impact Analysis
CVE-2026-119977 has a CVSS 3.1 base score of 8.1 (HIGH). It is remotely exploitable without authentication and without any user interaction, which puts every internet-facing WordPress site in the affected range at risk. The attack complexity is high because the attacker must time requests to coincide with a full-package core upgrade. Confidentiality, Integrity and Availability (High): code execution on the web server exposes the database credentials and site content, allows defacement or backdoors, and can take the site offline. Given the very large WordPress install base and the KEV listing, the vulnerability is attractive for mass exploitation campaigns.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-119977 in the wild by adding it to the KEV catalog; ransomware use is currently unknown. No reference is tagged as public exploit code, but Wordfence has published a technical advisory on the unauthenticated upgrade-window attack. The EPSS score of 1.2% (67th percentile) understates the urgency: the KEV listing and the size of the WordPress ecosystem call for immediate patching.
Remediation
- Follow the CISA KEV required action: apply mitigations in accordance with WordPress's instructions, comply with CISA BOD 26-04 and the CISA "Forensics Triage Requirements", or discontinue use of the product if mitigations are unavailable. The deadline was 2026-11-06.
- Update WordPress Core to 7.1.4 or, on older branches, to the fixed security release of your branch, for example 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11 or 6.5.14; fixes are available back to 4.7.39. See the WordPress 7.1.4 release notes.
- Until patched, block web access to the upgrade staging directories under wp-content (for example the upgrade folder) at the web server or WAF level, and avoid triggering full-package core upgrades on unpatched sites exposed to the internet.
- Check web server logs for requests to upgrade staging paths, look for unexpected PHP files in wp-content and the WordPress root, and compare core files against official checksums.
- As long-term hardening, run WordPress with least-privilege file permissions and disable PHP execution in directories that only need to hold uploaded or temporary files.
Technical Details
During a full-package core upgrade, WordPress downloads and unpacks the new release into staging paths that are both predictable and served by the web server, then moves the files into place. This is a TOCTOU race condition (CWE-367): the upgrader treats the staged content as trusted, but between creation and use the files can be reached and executed by others. An unauthenticated attacker who requests a staged installer script during this window can execute code on the server; the patched 7.1.4 code changes the logic in class-wp-upgrader.php and update-core.php. The CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H reflects network reachability without credentials, high complexity due to the timing requirement, and full impact on the affected system.
Frequently Asked Questions
Is CVE-2026-119977 being actively exploited?
Yes. CISA lists CVE-2026-119977 in the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild. Ransomware use is unknown, and the EPSS score is 1.2%.
What products are affected by CVE-2026-119977?
WordPress Core versions 4.7 through 7.1.3 are affected. Each maintained branch has a fixed release, from 4.7.39 up to 7.0.8 and 7.1.4.
How do I fix CVE-2026-119977?
Update WordPress Core to 7.1.4 or the fixed security release of your branch. Until then, block web access to the upgrade staging directories and check the site for unexpected PHP files.
How severe is CVE-2026-119977?
CVE-2026-119977 has a CVSS 3.1 score of 8.1, rated HIGH, and leads to unauthenticated remote code execution. Its EPSS score of 1.2% is in the 67th percentile, but the KEV listing confirms real-world attacks.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.