November 22, 2026

Critical WordPress Vulnerability Turns Core Update Process Into Attack Vector

To mitigate this, Umut Bayram and other security professionals have proposed several defensive strategies. The most effective immediate measure is to block all web access to the wp-content/upgrade directory via the web server configuration (such as .htaccess for Apache or a location block for Nginx). Because the WordPress updater works directly with the files on the server’s disk, it does not need the web server to serve those files to the public internet to complete the update. Blocking public access closes the door on the attacker without interfering with the patching process.

Another recommended path is the manual update. By performing an update outside of the web root—the folder served by the web server—administrators can ensure that no installer files are ever reachable via a URL. This involves backing up the site, unpacking the new WordPress release in a secure directory, and manually copying the core files into the live environment. While more labor-intensive, this method bypasses the automated updater entirely.

Crucially, Bayram warned that using the WP-CLI (WordPress Command Line Interface) for updates does not provide a workaround. The wp core update command triggers the same internal PHP classes and methods as the web-based updater, meaning it creates the same temporary folders in the same locations.

The Long-Term Outlook for Legacy Systems

This vulnerability also serves as a stark reminder of the dangers of running end-of-life (EOL) software. WordPress versions 4.6 and earlier no longer receive security updates and will not be patched for CVE-2026-119977. Bayram noted that the underlying flaw appears to date back as far as WordPress 2.7, which was released in 2008. For sites still running these ancient versions, the only path to security is a full migration to a supported release.

As the WordPress ecosystem continues to evolve, the complexity of its update mechanism remains a point of scrutiny. The discovery of CVE-2026-119977 underscores a fundamental challenge in software security: the "trusted" processes used to maintain a system are often the most attractive targets for exploitation. By understanding the nuances of how these updates occur—such as the difference between partial and complete packages—site administrators can better prepare their defenses against an increasingly automated threat landscape.

The final word from the research community is one of cautious diligence. While the fix in version 7.1.4 resolves the issue for future updates, the transition to that version represents a critical hurdle. Whether through blocking directory access or opting for manual file replacement, administrators are urged to take proactive steps before clicking the "Update Now" button.