CVE-2026-119977
🔴 High In CISA KEVWordPress Core (WordPress Foundation). Four preconditions must all hold, which is what the AC:H reflects: an affected version ; core updates applied through the WordPress updater ; wp-content/upgrade/ web-accessible and executing PHP ; and the attacker reaching the staged files between unpacking and cleanup. No account, no privileges and no user interaction are needed · 4.7.0 through 7.1.3, written in the record as 25 separate branch ranges (4.7.0 up to and including 4.7.38, 4.8.0 up to and including 4.8.33, and so on to 7.1.0 up to and including 7.1.3)
76.09th percentile
due 2026-11-06
Exploitation
Timeline
- 31/10/2026CVE record published (CVE List)
- 03/11/2026Added to the CISA KEV catalogue
- 04/11/2026WordPress Core — CISA confirms active exploitation, CVSS 8.1
- 05/11/2026WordPress Core actively exploited during upgrades
- 06/11/2026CISA deadline for US federal agencies
- 09/11/2026WordPress Core "WP2Shell" unauthenticated RCE
Risk
wp-content/upgrade/wordpress-7.1.4. wp-admin/setup-config.php refuses to run only when wp-config.php already exists, and release packages ship wp-config-sample.php instead, so the staged installer runs. An unauthenticated attacker submits database settings, the wizard writes a wp-config.php into the staging tree, and the staged admin screens, which include plugin and theme upload, give PHP execution. Before 7.1.4 the copy step skipped only wp-content and wp-includes/version.php, so the attacker's wp-config.php could be copied to the site root and execute on every request afterwards)Fix
b625b2d49c6a in 7.1.4 of 28/10/2026, backported to every branch eligible for security fixes, back to 4.7: 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 and 4.7.39 (WordPress 7.1.4, which carries 13 security fixes in all ; sites with automatic background updates enabled start the update themselves). Two things to carry into practice. Applying the update is itself exposed for the seconds it takes, so on an unpatched site block web access to /wp-content/upgrade/ first: nginx location ^~ /wp-content/upgrade/ { return 403; } or Apache RedirectMatch 403 ^/wp-content/upgrade/. The index.php that WordPress writes there stops directory listing only, not direct requests. To hunt retrospectively, search access logs for requests to PHP files under wp-content/upgrade/, above all setup-config.php, decoding percent-encoded paths first, and run find wp-content/upgrade -name "*.php" : the only expected file is an index.php containing // Silence is golden., so any other PHP file there, and a wp-config.php especially, needs investigationOfficial 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE-367