Skip to content
NewA calmer, faster ZeroHour
Exploit / PoChighExploited in the wild

WordPress update RCE attacked hours after the 7.1.4 patch

Original title: Hackers Actively Exploiting WordPress Remote Code Execution Flaw Just Hours After Patch Release

Cyber Security Newsby Abinaya ()2 min read1
Part of a story covered by 9 sourcesWordPress 7.1.4 fixes upgrade-window RCE as probes surgeMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Wordfence logged more than 18,500 requests to temporary installer paths in 21 hours; Core 4.7 through 7.1.3 is affected.

WordPress 7.1.4, released October 28, 2026, fixes 22 issues, including an unauthenticated code-execution flaw in the update process reported by Umut Bayram. Affected Core versions 4.7 through 7.1.3 unpack a complete package into a predictable folder under wp-content/upgrade; if that path allows public PHP execution, an attacker can hit the staged installer before cleanup. Wordfence deployed a firewall rule about three hours after the release and saw the first matching request nine minutes later. The report records exploitation attempts but not how many sites were breached.

Unconfirmed: The monitoring shows exploitation attempts but does not establish how many sites were successfully breached.

Key facts
  • The flaw has a CVSS score of 8.1, according to the supplied report.
  • In lab tests the temporary folder stayed available for only seconds.
  • The patch randomizes the staging folder, adds an index guard, and blocks unsafe staged configuration handling.
  • Wordfence free users are scheduled to get the rule on November 27, 2026.
  • The release also fixes stored cross-site scripting, information disclosure, and permission issues.
Security assessment · AI, from the articleExploited in the wild

Impact: Unauthenticated remote code execution during a Core update

ProductAffectedFixed in
WordPress Core4.7 through 7.1.37.1.4; fixes also for older branches through 4.7
What to do
  1. 1.Install WordPress 7.1.4 or the fixed release for the installed branch.
  2. 2.Review requests to PHP files beneath wp-content/upgrade and unexpected admin accounts, plugins, or files.
  3. 3.Enable Wordfence Extended Protection so the firewall loads before directly requested PHP.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at cybersecuritynews.com

A WordPress remote code execution vulnerability came under attack just hours after version 7. 1. 4 was released on October 28, 2026, fixing 22 vulnerabilities, including an unauthenticated code execution flaw in the update process.

Cyber Security News

By Abinaya · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.