CISA flags exploited WordPress Core race condition allowing code execution during upgrades
On 3 November 2026 CISA added CVE-2026-119977, a WordPress Core flaw that lets an unauthenticated attacker run code on the server during a core upgrade, to its Known Exploited Vulnerabilities catalogue. Every organisation running WordPress is concerned, and US federal agencies must act by 6 November.
What to do now
- Product
- WordPress Core
- Affected versions
- —
- CVE
- CVE-2026-119977
CISA has listed CVE-2026-119977, a vulnerability in WordPress Core, in its Known Exploited Vulnerabilities catalogue as of 3 November 2026. The flaw is a time-of-check time-of-use race condition (CWE-367) that can let an attacker with no account on the site execute code on the underlying server.
The weakness shows up during full-package core upgrades. While WordPress stages the new files, it uses intermediate directories whose paths are predictable and reachable from the web. An attacker who strikes during that short upgrade window can take advantage of the gap between when files are checked and when they are used.
The references attached by CISA point to the vendor's WordPress 7.1.4 release announcement and to a Wordfence entry describing unauthenticated remote code execution through the staged installer. CISA's entry does not itself list the affected versions, so administrators should confirm the scope in the WordPress announcement.
CISA asks organisations to apply the vendor's mitigations in line with its BOD 26-04 directive and its forensic triage requirements, meaning exposed systems should be checked for compromise, not just patched. The deadline for US federal agencies is 6 November 2026. Whether the flaw has been used in ransomware campaigns is listed as unknown.
Organisations outside the US federal scope should still treat the listing as a priority signal: the vulnerability is being exploited in the wild, and internet-facing WordPress sites are the obvious targets.
What to do now
- Update WordPress to version 7.1.4 or later, the release referenced by CISA, after confirming in the vendor announcement that it addresses CVE-2026-119977.
- Inventory every internet-facing WordPress site, including those with automatic core updates enabled.
- Check servers that recently ran a full core upgrade for signs of compromise, such as unexpected PHP files or unusual processes.
- As general good practice, review web server logs for requests targeting upgrade staging directories during upgrade windows.