Most of us still treat WordPress core updates as something for the next maintenance night. The October 28 security release is a good reason to rethink that. This is a WordPress RCE vulnerability exploited patch story in the most practical sense. According to Wordfence, attackers began probing for the flaw within hours of the fix shipping and kept at it all night. If your upgrade window is measured in days, the attackers’ window is wider than you think.
WordPress RCE Vulnerability Exploited Patch: What WordPress Shipped
WordPress.org published WordPress 7.1.4 on October 28, 2026, describing it as a security release and recommending that sites “update your sites immediately.” The first item on its list is “a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window,” reported by Umut Bayram. The release fixes a long list of other issues too, mostly stored cross-site scripting, plus an information disclosure issue and a root certificate update. WordPress says the security fixes were backported to all branches eligible for security fixes, currently through 4.7.
The Flaw, According to Wordfence
Wordfence’s analysis, published October 29, lists the issue as CVE-2026-119977. It affects WordPress Core 4.7.0 through 7.1.3 and carries a CVSS rating of 8.1 (High). Patched versions run across every branch, from 4.7.39 up through 6.8.12, 6.9.11, 7.0.8, and 7.1.4. WordPress.org’s own release post does not list CVE identifiers, so the CVE and score here are Wordfence’s.
The mechanism is unusual. During a Core update that uses a complete WordPress package, affected versions unpack the new files into a predictable directory beneath wp-content/upgrade, and that temporary copy includes the WordPress installer. As Wordfence puts it, “Because the staging directory is web-accessible on many servers, an unauthenticated attacker who requests the installer at precisely the right moment can interact with the staged WordPress copy and progress to PHP code execution.”
Wordfence is clear that this is hard to pull off. An attacker needs a full-package update, public web and PHP access to the staging tree, a predictable or discovered path, and enough time before cleanup. “In lab environments, the vulnerable staging directory normally remained available for only seconds.” Wordfence says 7.1.4 fixes it by “randomizing the staging directory, adding an index guard, and preventing unsafe promotion of staged configuration data.”
How Fast the Attempts Started
Here are Wordfence’s own numbers. Its team deployed a firewall rule on October 28 at 20:30 UTC, “approximately three hours after WordPress announced the security release.” Then: “The first match for our new firewall rule arrived nine minutes after deployment. During the first 21 hours, we recorded more than 18,500 requests targeting staged setup-config.php installer paths.”
Wordfence describes how the attackers behaved: “Two of the largest sources repeatedly polled small groups of sites for roughly 14.5 hours, behavior consistent with trying to catch the brief upgrade window.” It also adds a fair caveat: “Not every request used the exact vulnerable path.” These are attempts and probes. Wordfence’s post does not report confirmed site takeovers, and neither will I.
Why does this matter if the window is only seconds? Because the attacker is not betting on one request. Repeated polling is a bet that your update happens while they are watching. The race only exists during an update, which turns the upgrade process itself into the attack surface. Slow, ad hoc, or staggered upgrades give polling attackers more opportunities.
Shrinking Your Upgrade Window: My Checklist
These are my recommendations for teams running WordPress at scale, built on WordPress.org and Wordfence guidance. They are not an official checklist.
- Verify, do not assume. Wordfence recommends going to Dashboard > Updates and confirming each site is on 7.1.4 or the patched release for its branch. Across a fleet, check versions centrally with WP-CLI or your management tool, and look for sites where auto-updates are disabled or failed.
- Let background updates do their job. WordPress says sites that support automatic background updates will begin updating automatically. If you have turned those off for “stability,” treat security releases as an exception with a fast, tested path.
- Block web access to the staging directory. The staging tree only matters because it is web-accessible on many servers. Deny public HTTP and PHP execution under wp-content/upgrade at the web server or WAF. I would do this permanently, not just this week.
- Put your WAF in front of PHP, not behind WordPress. Wordfence notes this exploit requests a staged PHP file directly without loading WordPress. Its firewall needs “Extended Protection” to see those requests. Whatever WAF you use, make sure it inspects direct PHP requests.
- Hunt if you were slow. Wordfence advises reviewing for unexpected requests to PHP files beneath wp-content/upgrade, unfamiliar administrator accounts, unexpected plugins, or PHP files you did not place there.
- Set a security-release SLA in hours. Write down that core security releases go out the same day. Measure it, and treat misses like incidents.
- Retire unsupported branches. WordPress reminds users that only the most recent version is actively supported, and Wordfence notes 4.6 and earlier get no security updates.
Consider this hypothetical. An agency manages 200 client sites and pushes core updates manually every Friday night. A security release lands on Wednesday. For two days, unpatched sites carry a known RCE, and every one of those Friday updates opens a fresh race window while polling attackers are already watching. Same-day automated updates plus a blocked staging path close both gaps.
The Bottom Line
WordPress shipped the fix on October 28. Wordfence saw the first matching attempts within hours and logged more than 18,500 requests in 21 hours. The exploit is hard, and Wordfence reports attempts, not confirmed compromises. But the speed of the probing is the lesson: your patch window should be measured in hours.

Leave a Reply