Zero Day Room
Live
Vulnerabilities

WordPress CVE-2026-119977 Exploit Requires Immediate Directory Block

A critical race condition in WordPress core, CVE-2026-119977, allows unauthenticated attackers to execute server-side code during the update process.

A critical race condition in WordPress core, CVE-2026-119977, allows unauthenticated attackers to execute server-side...

A high-severity race condition in the WordPress core updater, tracked as CVE-2026-119977, allows unauthenticated attackers to execute PHP code on the server during the brief unpacking of an update. With a CVSS score of 8.1, this vulnerability affects WordPress versions 4.7 through 7.1.3 and can be exploited without any user account or stolen credentials. The flaw has existed in the platform's code since version 2.7 was released in 2008, and it is now being actively exploited in the wild.

CISA Mandates Immediate Action for Federal Agencies

The Cybersecurity and Infrastructure Security Agency added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 3. The agency has set a binding deadline of November 6 for all U.S. federal civilian agencies to apply the available patches or mitigations. This action shows the immediate risk the vulnerability poses to critical infrastructure and public-facing services.

Patch Availability and Partial Update Risks

WordPress released version 7.1.4 with a fix for the flaw. The organization also backported security updates for every older maintenance branch from 4.7 to 7.1, making fixes available for a wide range of installations. However, sites running versions 7.1 through 7.1.3 receive partial update packages that do not include the vulnerable installer file. These sites remain at risk if the underlying core updater code itself has not been patched. WordPress versions 4.6 and earlier no longer receive security updates and have no official fix for this vulnerability.

Exploitation Window and Mitigation Requirements

Attackers exploit a predictable file path during the update process. On WordPress 5.9 and later, the temporary folder used during updates is named after the downloaded file, making its location easy to guess. An attacker can run code by accessing the installer script in the wp-content/upgrade/ directory before WordPress deletes it. The window for this attack lasts only seconds. While WordPress 7.1.4 introduces a random folder name, this fix cannot protect sites that are using unpatched code to unpack updates. Using the WP-CLI wp core update command is not a safe alternative, as it uses the same vulnerable updater code.

The primary mitigation is to immediately block web access to the wp-content/upgrade/ directory via server configuration, such as a .htaccess rule for Apache or a corresponding directive for Nginx. This step prevents exploitation during the critical seconds of the update process. Administrators on versions 2.7 through 7.0.7 and 7.1 through 7.1.3 are advised not to click 'Update Now' before applying this pre-update hotfix. Denying web access to the upgrade directory is the critical control to stop this exploit.

Related coverage

More from Vulnerabilities