WordPress vulnerability targeted during core upgrade window
A WordPress vulnerability tracked as CVE-2026-119977 is being actively targeted during core upgrades. The flaw affects WordPress 4.7 through 7.1.3 and can enable unauthenticated remote code execution, meaning an attacker who has not logged in may be able to run malicious code on the web server. The WordPress Security Team addressed it on October 28, 2026, in WordPress 7.1.4 and security releases for older branches. Wordfence rates the vulnerability 8.1, or High, under the Common Vulnerability Scoring System (CVSS), a standard scale for assessing security flaws.
The vulnerability exists because full-package WordPress upgrades use predictable staging paths that are accessible from the web. A staging directory is a temporary folder where installation files are prepared before an update finishes. During that brief period, an attacker can request installer files beneath `/wp-content/upgrade/`. Wordfence observed requests such as `GET /wp-content/upgrade/wordpress-6.9.11/setup-config.php`, sent in an attempt to reach an installer while the relevant site was updating. If the request arrives at the right moment, the attacker can complete the staged installation, create an administrator account and upload malicious PHP code, which is code the server runs to produce website pages and functions.
This is a race condition, where success depends on performing an action within a short and unpredictable window. The attacker must reach the temporary installer while the upgrade is underway and finish the attack before WordPress removes the staging directory. That makes successful exploitation difficult in practice, but the potential outcome is complete site compromise. An attacker who establishes access could install backdoors, which are hidden ways to regain entry, alter site content or extract sensitive data.
Updating presents an unusual but important detail. Moving from a vulnerable release to a fixed release runs the vulnerable upgrade process one final time. However, that exposure lasts only for the duration of the update, and subsequent upgrades are no longer affected after the patched version is installed. Wordfence therefore recommends updating immediately rather than leaving the site on a vulnerable release. As an extra precaution, access to PHP files inside `/wp-content/upgrade/` can be blocked at the web-server level before the update begins. Site owners who do not administer their own server can ask their hosting provider to apply that restriction. Sites with automatic background updates enabled should already have received a fixed release.
The patched versions listed by Wordfence 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. A site remaining on an older branch should install the corresponding security release rather than assuming only WordPress 7.1.4 contains a fix. The vulnerability was also added to the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog on November 2, 2026.
Wordfence says its firewall blocked more than 240,000 exploit attempts after public disclosure. Targeting began on October 28, initially at low volume, before reaching its highest levels between October 29 and November 1. The peak came on October 30, when more than 74,000 requests were blocked in one day. These figures do not represent 240,000 compromised websites. Wordfence says most requests were probably automated probes sent to the predictable path in the hope of coinciding with a site's short upgrade window.
The most active addresses in Wordfence's data 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. The remaining listed addresses 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. These addresses should be treated as especially suspicious when found requesting upgrade-directory files.
Site owners and administrators should examine web-server access logs, the records of requests received by a website, for requests to PHP files beneath `/wp-content/upgrade/`, especially `setup-config.php`. Wordfence notes that legitimate upgrades do not require outside requests to those files. Administrators should also inspect that directory for leftover files or folders and review installed plugins and WordPress user accounts for unexpected additions. Missing log entries do not prove that a site escaped compromise.
If suspicious activity is found, unexpected files, plugins and unknown administrator accounts should be removed, followed by a broader search for backdoors. Because deleting only the first visible malicious file may leave another route into the site, this review needs to cover the full installation. Backups should also be checked before restoration so that compromised material is not simply returned to service.
Wordfence Premium, Wordfence Care and Wordfence Response received a rule against known exploits on October 28. The free Wordfence version was scheduled to receive it on November 27, 30 days later. Because the targeted PHP files run independently and do not load WordPress itself, Wordfence says its firewall must be optimized and operating in Extended Protection mode to inspect these requests. That distinction matters during the update window and should be verified rather than assumed.
For site owners who prefer not to manage hosting infrastructure themselves, AEU Hosting provides managed WordPress hosting secured end to end. Regardless of hosting arrangement, the immediate priorities are to install the appropriate patched WordPress release, restrict outside access to upgrade-directory PHP files during that update, and investigate any evidence that the temporary installer was reached.
Also available in: Italiano