AEGLIX News
A security fix released for an actively exploited WordPress vulnerability can itself expose websites to attack during the update process, according to research findings. The flaw, tracked as CVE-2026-119977, affects WordPress versions 4.7 through 7.1.3 and allows unauthenticated remote code execution via predictable, web-accessible staging paths used during full-package core upgrades. WordPress issued version 7.1.4 and corresponding patches for older branches back to 4.7 to address the issue, but the update mechanism retains a window of exposure on certain versions.
The vulnerability stems from the use of predictable temporary folder names during core updates. While the patch assigns a random name to the upgrade folder, sites running WordPress 5.9 or later can still generate a predictable folder name during the specific update that installs the fix. Complete update packages always include installer files that create this exposure, whereas partial packages only pose a risk if they happen to contain those files. On versions 4.4 through 5.8, legacy code adds random characters to the folder name unless the site leaks the path through other means. WordPress 4.6 and earlier no longer receive security updates and remain without a fix for this flaw.
Active exploitation attempts began rapidly after the patch release. Wordfence observed attack attempts starting nine minutes after deploying a firewall rule for the vulnerability on release day, with two active sources scanning sites for approximately 14.5 hours. The researcher also determined that using WP-CLI's 'wp core update' command is not a safe alternative, as it runs the same underlying updater and unpacks files into the same web-reachable folder, preserving the exposure window during the update process.
WordPress has released version 7.1.4 and matching updates for branches back to 4.7 to remediate the underlying vulnerability. The researcher recommends blocking web access to the wp-content/upgrade directory via web server configuration before applying the update to mitigate the temporary exposure during installation. Administrators should be aware that WP-CLI updates do not bypass this risk, as they utilize the same vulnerable updater mechanism. Sites on WordPress 4.6 and earlier have no available patch and should be upgraded to a supported branch immediately.
Report prepared 2026-11-06 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.