Attackers Probe WordPress Upgrade Flaw Within Minutes of Firewall Rule Going Live

WordPress upgrade bug probing person typing code laptop

Attackers began probing a fresh WordPress upgrade flaw within minutes of its firewall rule going live. Wordfence, the security firm behind the WordPress firewall, tracked the surge, and SecurityWeek reported the timeline, and the WordPress upgrade bug probing started nine minutes after Wordfence deployed its rule on October 28. Wordfence counted more than 18,500 requests to staged installer paths in the opening 21 hours.

The flaw sits in the WordPress core update process, and it affects versions 4.7 through 7.1.3. During a full package core upgrade, affected versions, however, unpack new files into a predictable folder under the upgrade directory, and that staging folder can stay web accessible on many servers, and it holds the WordPress installer, but an attacker with no account who hits the staged installer at the right moment can interact with the staged copy and reach code execution.

The WordPress upgrade bug probing window is narrow, and that narrowness cuts both ways. Wordfence lab tests put the staging window at seconds, and a single random request rarely lands. Attackers answered with volume, and two large sources polled small groups of sites for about 14.5 hours, and a bot that polls one site every few seconds can catch a short upgrade window that a lone request would miss.

WordPress upgrade bug probing laptop code screen developer
Code fills a laptop screen in this file photo from Lune Studio.

WordPress 7.1.4 fixes the flaw, and backports cover older branches down to 4.7, and the fix randomizes the staging directory name, adds an index guard, and blocks unsafe promotion of staged configuration data, and the release also fixes 22 security issues in total, including stored cross site scripting and information disclosure flaws. However, a firewall rule alone does not replace the update, for the exploit hits a staged PHP file directly.

Wordfence Premium, Care, and Response customers got the WordPress upgrade bug probing rule on October 28, about three hours after release. Free users face the standard 30 day delay, with the rule due on November 27. Wordfence also notes its firewall must run in Extended Protection mode to catch these requests before they reach the file, and the WordPress upgrade bug probing counts show why delay carries risk, even when the window looks tiny.

No successful compromise is confirmed in public reports yet, and that line matters. Probing and attempts are not proof of a break in, and site owners should not read request counts as breach counts, but the absence of a confirmed case does not mean safety, for a quiet break in leaves few public traces. The GitHub security advisory for the flaw carries a Low label, but Wordfence scores it 8.1 High, so teams should patch on the higher caution, and a Low label alone would understate the probing volume.

WordPress upgrade bug probing code security screens
Code and security graphics fill screens in this file photo from SecurityWeek.

Site owners can check WordPress upgrade bug probing exposure with a few plain steps, and the PHP flaws threatening websites shows how server side bugs can hit millions of sites at once. CISA KEV deadline for PHP flaws shows exploited lists move fast once a flaw goes public, and the PHP2Shell attack on servers shows chained flaws can root servers when patches lag.

First, confirm version 7.1.4 or the matching branch backport through the dashboard updates screen. Second, search access logs from October 28 onward for requests to setup config paths under the upgrade folder. Treat any hit during an upgrade window as a reason to inspect the site, for the WordPress upgrade bug probing pattern rewards fast log review.

Disable PHP execution in the upgrade staging folder where the server allows it, and a staged installer file cannot run even when a request reaches it, and by contrast, a server that serves and runs staged files hands attackers the exact path they poll for. After that, log review should become routine after every core update.

WordPress powers a huge share of the web, and upgrade flaws touch that whole share at once, and the probing began in minutes, the fix is live, and the next step is simple, but the WordPress upgrade bug probing story closes with an update, a log check, and no room for delay. Above all, the update comes first, and the log check comes next. A patched site with checked logs beats a fast site with blind spots.

Stay Connected with The MES Times

Get the latest tech, AI and gadget news and updates wherever you prefer.

Follow on Google Discover

Add The MES Times to Preferred Sources and see more of our stories in Google Search and Top Stories.

AI & Emerging Tech

Aizaz Khan is a technology journalist at The MES Times, leading coverage on artificial intelligence, humanoid robotics, and silicon hardware. Holding a degree in AI and Robotics where he graduated top of his class he approaches tech reporting with an engineer's eye rather than PR talking points. His work focuses on dissecting research papers, neural model architectures, and physical robotics systems to explain their real-world impact and limitations.

0 comments Oldest comments first