Threat Feed

CVE-2026-119977: WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability

Exploitation: In the wild · CVSS 8.1 High · Unauthenticated · Published 2026-10-31

Description

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.

Enclave's analysis

CVE-2026-119977 is a CWE-367 TOCTOU race in WordPress Core 4.7 through 7.1.3. During a full-package core upgrade, files are unpacked into a predictable directory under wp-content/upgrade, and that copy includes the installer wp-admin/setup-config.php. If the staging tree is web-reachable and executes PHP, an unauthenticated attacker who requests the staged installer before cleanup can reach code execution as the web-server user. The exposure window is only the seconds the staging directory exists during an update, and it needs a server configuration that exposes that path. CISA KEV lists the CVE (added 2026-11-03) and SSVC shows Exploitation=active and Automatable=no. Wordfence reported more than 18,500 requests for staged setup-config.php paths in the first 21 hours. These are attempts seen by the firewall, not confirmed compromises. No public PoC was found. WordPress's own advisory rates the issue Low, and Patchstack reportedly considers it impractical. The CVSS of 8.1 (AC:H) reflects the race. EPSS is low (0.006). Fixed in 7.1.4 and backports on older branches. Blocking HTTP access to /wp-content/upgrade/ before updating is the recommended mitigation.

Fix

Upgrade WordPress Core (WordPress Foundation) to 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31, 4.9.35, 4.8.34, 4.7.39 (per secondary sources; the WordPress release post says backports 'will ship as they become ready'). Versions before 4.7 are reported to get no fix.. No fixed version is listed for WordPress; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
WordPress4.7.0 through 4.7.38Not listed
WordPress4.8.0 through 4.8.33Not listed
WordPress4.9.0 through 4.9.34Not listed
WordPress5.0.0 through 5.0.30Not listed
WordPress5.1.0 through 5.1.27Not listed
WordPress5.2.0 through 5.2.29Not listed
WordPress5.3.0 through 5.3.26Not listed
WordPress5.4.0 through 5.4.24Not listed
WordPress5.5.0 through 5.5.23Not listed
WordPress5.6.0 through 5.6.22Not listed
WordPress5.7.0 through 5.7.20Not listed
WordPress5.8.0 through 5.8.18Not listed
WordPress5.9.0 through 5.9.19Not listed
WordPress6.0.0 through 6.0.17Not listed
WordPress6.1.0 through 6.1.15Not listed
WordPress6.2.0 through 6.2.14Not listed
WordPress6.3.0 through 6.3.13Not listed
WordPress6.4.0 through 6.4.13Not listed
WordPress6.5.0 through 6.5.13Not listed
WordPress6.6.0 through 6.6.10Not listed
WordPress6.7.0 through 6.7.10Not listed
WordPress6.8.0 through 6.8.11Not listed
WordPress6.9.0 through 6.9.10Not listed
WordPress7.0.0 through 7.0.7Not listed
WordPress7.1.0 through 7.1.3Not listed
WordPress Core (WordPress Foundation)4.7.0 through 7.1.3. The CVE lists each branch up to its last pre-fix release: 4.7.x to 4.7.38, 4.8.x to 4.8.33, 4.9.x to 4.9.34, 5.0.x to 5.0.30, 5.1.x to 5.1.27, 5.2.x to 5.2.29, 5.3.x to 5.3.26, 5.4.x to 5.4.24, 5.5.x to 5.5.23, 5.6.x to 5.6.22, 5.7.x to 5.7.20, 5.8.x to 5.8.18, 5.9.x to 5.9.19, 6.0.x to 6.0.17, 6.1.x to 6.1.15, 6.2.x to 6.2.14, 6.3.x to 6.3.13, 6.4.x to 6.4.13, 6.5.x to 6.5.13, 6.6.x to 6.6.10, 6.7.x to 6.7.10, 6.8.x to 6.8.11, 6.9.x to 6.9.10, 7.0.x to 7.0.7, 7.1.x to 7.1.3.7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31, 4.9.35, 4.8.34, 4.7.39 (per secondary sources; the WordPress release post says backports 'will ship as they become ready'). Versions before 4.7 are reported to get no fix.

Seen in 4 sources