Tens of Thousands of Attacks Target High-Severity RCE Flaw in WordPress Core Shortly After Patch Release

By Ravie Lakshmanan
October 30, 2026

Threat actors have swiftly mobilized to exploit a high-severity security vulnerability affecting WordPress Core, launching tens of thousands of automated probes just days after official patches were made public. The security flaw, which currently lacks a traditional CVE identifier, represents a critical remote code execution risk impacting a wide range of WordPress Core versions spanning from 4.7 through 7.1.3. Carrying a significant CVSS severity score of 8.1, the vulnerability requires urgent attention from web administrators worldwide, prompting the WordPress security team to rush out a dedicated patch release on October 28, 2026, designated as version 7.1.4.

The mechanism behind the flaw lies deep within the platform’s core upgrade architecture. According to security researchers at Wordfence, the issue stems from predictable and web-accessible staging paths that are automatically utilized during full-package core updates. This structural design inadvertently creates a window of vulnerability, making it technically feasible for unauthenticated remote attackers to execute arbitrary code on the underlying server environment during the active upgrade window.

WordPress RCE Flaw Draws Nearly 63,000 Attack Attempts in Just 24 Hours

To understand the mechanics of the threat, security analysts point to how WordPress handles major updates. Affected versions of the software unpack newly downloaded files—which form part of a complete core update—into a highly predictable directory structure located beneath the "wp-content/upgrade" folder. Crucially, this staging copy includes the core WordPress installer itself, a component normally restricted or executed under controlled administrative conditions during initial site setup.

Alex Thomas, who leads the Wordfence Threat Response Team, elaborated on how external actors can leverage this structural quirk. Because the staging directory remains web-accessible on a vast number of web servers, an unauthenticated attacker who manages to request the installer script at precisely the right moment can interact directly with the staged WordPress copy. By successfully initiating this interaction, the malicious actor can progress rapidly to PHP code execution, effectively hijacking the host server.

Executing this attack successfully, however, requires immense precision. Security experts note that successful exploitation hinges entirely on an attacker’s ability to hit a remarkably narrow temporal window—specifically, the exact moments while WordPress is in the process of unpacking a complete core update package. In standard laboratory environments and typical server settings, this vulnerable window has been observed to last for only a matter of seconds, making it a classic race condition.

Despite the fleeting nature of the upgrade window, malicious actors have waste no time attempting to automate and scale the exploitation process. Rather than relying on pure coincidence, threat actors are continuously polling vulnerable paths, such as the "setup-config.php" file, with high frequency in an aggressive attempt to catch sites mid-update. The scale of this automated scanning has proven to be immense. Over a recent 24-hour observation period, automated telemetry systems managed by Wordfence recorded and blocked an astonishing 62,969 distinct attack attempts targeting the WordPress Core vulnerability.

WordPress RCE Flaw Draws Nearly 63,000 Attack Attempts in Just 24 Hours

Detailed technical observations from the threat intelligence team reveal sophisticated probing patterns by multiple distinct threat groups. Two of the largest identified sources of malicious traffic were observed repeatedly polling small, targeted groups of websites for roughly 14.5 hours straight. This prolonged, methodical behavior is highly consistent with automated scripts attempting to patiently wait out and catch the brief, unpredictable upgrade window of target sites. In addition to simple polling, other malicious sources were seen testing a wide variety of different staging-directory layouts and version-name naming conventions in an effort to map out vulnerable configurations across diverse hosting environments.

While not every incoming request utilized the exact vulnerable path or succeeded in executing code, the sustained polling activity and exact-layout probes demonstrate that threat groups quickly reverse-engineered the underlying mechanics of the race condition. Attackers immediately recognized the tactical value of the flaw and adapted their scanning infrastructure to target it at scale almost immediately after technical details and patches became public.

Given the active and automated exploitation attempts currently underway across the broader internet, cybersecurity professionals and WordPress site administrators are strongly advised to take immediate defensive action. Site owners running any version between 4.7 and 7.1.3 should update their installations to version 7.1.4 as soon as possible to permanently close the vulnerability window.

In addition to applying the core update, administrators are encouraged to conduct thorough forensic checks of their server environments. Security teams should carefully review access and error logs for suspicious or unauthorized HTTP requests directed toward PHP files located within the "wp-content/upgrade" directory. Furthermore, routine audits should be performed to check for any unfamiliar administrator accounts, newly spawned plugins, or unauthorized PHP files that may have been successfully deployed during a successful exploit attempt before the patch was applied.