← All articles

WordPress RCE flaw draws 240,000 exploit attempts

WordPress RCE flaw draws 240,000 exploit attempts

A WordPress RCE flaw, meaning a remote code execution vulnerability that lets an attacker run code on a server, drew more than 240,000 blocked exploit attempts after its disclosure. Tracked as CVE-2026-119977, the high-severity flaw affects WordPress core versions 4.7 through 7.1.3. The WordPress Security Team addressed it on October 28, 2026, in WordPress 7.1.4 and equivalent security releases for older branches. Wordfence Intelligence assigned it a CVSS score of 8.1, or High. CVSS is a standard scale for rating the seriousness of security flaws.

An attacker does not need to sign in before attempting exploitation. The opportunity exists during a full-package WordPress core update because the upgrade process places installer files in predictable, publicly reachable staging locations under /wp-content/upgrade/. This creates a race condition, where success depends on acting within a short period while two processes overlap. Exploitation is therefore difficult in practice, but a successful attacker could run code on the server and take complete control of the site.

Wordfence observed attackers requesting installer files inside the staging directory while core upgrades might be running. One observed path was /wp-content/upgrade/wordpress-6.9.11/setup-config.php. If the staged installer is reachable at that moment, an attacker can finish the installation, create an administrator account and upload malicious PHP code. PHP is the programming language used to run much of WordPress on a web server. The resulting access could be used to add backdoors, alter site content or extract sensitive information.

According to Wordfence, targeting began on October 28, the day the vulnerability became public, although activity was initially limited. The heaviest volume occurred from October 29 through November 1. More than 74,000 attempts were blocked on October 30 alone, the highest single-day total reported. These numbers do not show that an equivalent number of websites were compromised. Wordfence assesses that most requests were probably automated probes aimed at the predictable path, hoping to coincide with an active update. An attacker must arrive during the brief upgrade window and complete the attack before WordPress removes the staging directory.

The most active addresses listed by Wordfence were 103.59.160.171 with more than 74,900 blocked requests, 2001:df1:e8c0::106b with more than 40,400, and 51.89.103.78 with more than 34,600. Other listed sources were 185.177.72.61 with more than 4,400, 195.3.220.7 with more than 2,900, 96.62.218.148 with more than 2,300, 20.217.186.29 and 87.58.197.83 with more than 2,000 each, 154.26.238.8 with more than 1,800, and 20.46.43.126 with more than 1,700.

The Cybersecurity and Infrastructure Security Agency added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 2, 2026. Site owners should install WordPress 7.1.4 or the corresponding fixed release for their existing branch. Automatic background updates should already have moved enabled sites to a patched version. Updating from an affected release does run the vulnerable upgrade process one final time, but only for the duration of that update. Once the patched release is active, later upgrades no longer contain this weakness, so postponing the update leaves the site exposed for longer.

As an extra precaution, administrators can block web access to PHP files inside /wp-content/upgrade/ before starting the update. Wordfence says its Premium, Care and Response customers received a firewall rule on October 28, while the free version was scheduled to receive it on November 27, 30 days later. Because the targeted PHP files run independently and do not load WordPress, the Wordfence firewall must be optimized and operating in Extended Protection mode to examine and stop those requests. Wordfence says Premium, Care and Response sites using that configuration are protected during the update.

Fixed releases are 4.7.39, 4.8.34, 4.9.35, 5.0.31, 5.1.28, 5.2.30, 5.3.27, 5.4.25, 5.5.24, 5.6.23, 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, 6.6.11, 6.7.11, 6.8.12, 6.9.11, 7.0.8 and 7.1.4. Owners should verify the installed version rather than assume an automatic update completed.

Investigators should examine web server access logs, the records of requests received by a website, for access to PHP files beneath /wp-content/upgrade/, especially setup-config.php. Wordfence says legitimate upgrades do not require outside requests to those files. Administrators should also look for leftover upgrade files or directories, unfamiliar plugins and unknown WordPress users, particularly administrator accounts. Unexpected files, plugins and accounts should be removed, and the site should be checked for backdoors, which are hidden ways for an attacker to regain access. A lack of suspicious log entries does not prove that the site was untouched.

Wordfence says its Care and Response services include hands-on incident support, with Response available continuously and carrying a one-hour response time. For website owners who want the WordPress environment managed rather than maintained alone, AEU Hosting provides managed WordPress hosting secured end to end. Regardless of hosting arrangement, the immediate priorities are to use a listed patched release, protect the final vulnerable update where possible and investigate any unexplained requests to the upgrade directory.

Also available in: DeutschItalianoShqip