Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Wordfence title card reading WordPress 7.1.4 Patches Unauthenticated Upgrade-Window RCE; Exploitation Attempts Detected After Release, beside a WordPress 7.1.4 logo.
Image: Wordfence (fair use). Title card from Wordfence's advisory on WordPress 7.1.4.

Response

Wordfence Says Attackers Started Hunting a WordPress Core Update Race Within Hours of the 7.1.4 Fix, Sending More Than 18,500 Requests in 21 Hours to Catch a Window That Lasts Seconds

The unauthenticated flaw, rated 8.1, lets an attacker who requests the staged installer during a full Core update work toward PHP code execution. WordPress fixed it in 7.1.4 and backported the change to every branch back to 4.7; Wordfence says site owners should confirm the update landed and check wp-content/upgrade for stray requests.

Noah Park, ResponseNew York5 min read

NEW YORK - Attackers began trying to exploit a newly patched flaw in the WordPress update process within hours of the fix, according to the WordPress security firm Wordfence. The bug, fixed in WordPress 7.1.4 on Oct. 28, lets an unauthenticated attacker reach remote code execution if a request lands during the few seconds a site spends unpacking a full Core update.

Wordfence said the first request matching the firewall rule it wrote for the flaw arrived nine minutes after the rule was deployed. "During the first 21 hours, we recorded more than 18,500 requests targeting staged setup-config.php installer paths," the company wrote.

WordPress described 7.1.4 as a security release and recommended that sites update immediately. Wordfence counts 22 vulnerabilities fixed in it. The upgrade-window flaw, reported by the researcher Umut Bayram, is rated 8.1, high, and affects WordPress 4.7.0 through 7.1.3. No CVE identifier had been assigned as of SecurityWeek's report on Friday.

A race against cleanup

Wordfence vulnerability card for WordPress Core 4.7.0 - 7.1.3, Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution, rated CVSS 8.1, listing the patched versions from 4.7.39 through 7.1.4 and crediting researcher Umut Bayram.
Image: Wordfence (fair use).Vulnerability details from Wordfence's advisory, captured Oct. 30, 2026.

During a Core update that uses a complete WordPress package, affected versions unpack the new files into a predictable directory beneath wp-content/upgrade, Wordfence explained. That temporary copy includes the WordPress installer. On many servers the staging directory is reachable from the web, so an attacker who requests the installer at the right moment can interact with the staged copy and work toward PHP code execution.

The conditions are narrow. "The attacker needs a full-package update containing the installer files, public web and PHP access to the staging tree, a predictable or discovered staging path, and enough time to complete the attack before WordPress cleans up the temporary files," Wordfence wrote. In lab environments, the vulnerable directory normally stayed available for only seconds. A single request is unlikely to succeed, the company said, but repeated automated polling improves the odds.

WordPress 7.1.4 randomizes the staging directory, adds an index guard and prevents unsafe promotion of staged configuration data. The fix was backported to every affected branch back to 4.7, with patched releases running from 4.7.39 to 7.0.8 on the older lines.

What the attack traffic looks like

Wordfence advisory section titled Active Exploitation Is Already Underway, reporting that the first match for its new firewall rule arrived nine minutes after deployment, that it recorded more than 18,500 requests targeting staged setup-config.php installer paths in the first 21 hours, and that two of the largest sources polled small groups of sites for roughly 14.5 hours.
Image: Wordfence (fair use).Exploitation telemetry from Wordfence's advisory, captured Oct. 30, 2026.

The traffic Wordfence describes is persistent rather than broad. 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," the company wrote. Other sources cycled through variations of staging-directory and version names. Not every request used the exact vulnerable path, Wordfence said, but the sustained polling and probes matching the real directory layout showed that attackers had quickly understood the race condition.

That pattern matters for anyone reading web logs. A site that is being polled may show a steady stream of requests for setup-config.php under wp-content/upgrade over many hours, long before an update gives the attacker a window to hit.

Wordfence deployed its firewall rule for paying customers at 20:30 UTC on Oct. 28, about three hours after WordPress announced the release; users of its free plugin receive it on Nov. 27 under the company's standard 30-day delay. Because the exploit requests a staged PHP file directly without loading WordPress, Wordfence said its firewall only sees the request if it is configured with Extended Protection, and it stressed that the rule does not replace the update.

The rest of the release

WordPress.org News post for WordPress 7.1.4, dated October 28, 2026, by Aaron Jorbin, describing a security release with fixes for multiple issues and recommending that sites update immediately.
Image: WordPress.org (fair use).The WordPress 7.1.4 release announcement, captured Oct. 30, 2026.

The release announcement on WordPress.org lists the other fixes: multiple stored cross-site scripting bugs in block markup, the Categories block, comments pagination blocks, Customizer selective refresh, privacy data removal requests, crafted user logins and the Playlist and Image blocks; several Interactivity API issues, including a stored denial of service; a flaw that let unauthenticated users discover unpublished Customizer changesets; and a weakness that let some privileged users read Notes on posts they cannot edit. Two of the cross-site scripting reports are credited to Anthropic. The release also updates the bundled root certificates after the eMudhra revocation.

Most of those bugs require an authenticated Contributor, Author or Editor account, Wordfence noted, which lowers their exposure compared with the upgrade-window flaw.

What responders should do

Most WordPress sites receive security releases through automatic background updates, but Wordfence recommends checking rather than assuming. Its guidance for site owners and the teams that run WordPress fleets:

  • Confirm each site is on 7.1.4 or the patched release for its branch. WordPress 4.6 and earlier no longer receive security updates.
  • Review web and server logs for unexpected requests to PHP files beneath wp-content/upgrade if a site stayed unpatched, and look for unfamiliar administrator accounts, unexpected plugins or PHP files nobody placed there.
  • Treat a web application firewall as a stopgap while updating, not a substitute.
  • Scan sites after updating for unexpected Core changes or malicious files.

Sources:


Noah Park covers incident response and blue-team operations for SOCtember from New York.

Related stories

Response desk