WordPress 7.1.4 Fixes 22 Security Issues, Including an Upgrade-Process RCE Risk — Update in a Window You Control

WordPress 7.1.4 Fixes 22 Security Issues, Including an Upgrade-Process RCE Risk — Update in a Window You Control

WordPress 7.1.4 Fixes 22 Security Issues, Including an Upgrade-Process RCE Risk — Update in a Window You Control

WordPress has shipped version 7.1.4, a short-cycle security release that fixes 22 vulnerabilities — some of which, per coverage of the release, have been sitting in core since WordPress 4.7 nearly a decade ago. Released on October 28 and led by Aaron Jorbin and Nik Tsekouras, the update is recommended for immediate deployment: sites with automatic background updates will already be applying it, and everyone else should move deliberately rather than defer. The next major version, 7.2, is planned for December 8.

The headline fix is unusual: a weakness in the WordPress upgrade process itself that can lead to remote code execution during the upgrade window, reported by Umut Bayram. In other words, the act of updating — the one operation every security article tells you to do constantly — briefly widened the attack surface. WordPress did not attach a CVE to the release post, and the project's writeup does not claim active exploitation; the practical takeaway is that the upgrade path is attack-relevant code, not infrastructure plumbing, and that the window between "update started" and "update finished" deserves the same monitoring attention as any other privileged endpoint.

The rest of the batch is dominated by stored XSS — twelve credited reports in the release notes. The list: stored XSS via specially crafted block markup (Rafie Muhammad of Awesome Motive); a stored XSS in Privacy Data Removal Requests; multiple stored XSS issues in the Interactivity API, found independently by AnC and DatNLQ of VietSunshine Cyber Security, rekter0, Anas cherni, Marcel Karlsson, and the WordPress Security Team's own Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz; a stored denial-of-service issue in the Interactivity API; stored XSS in Customizer selective refresh and in the Categories block (Ben Bidner); stored XSS from specially crafted user logins; stored XSS in Playlist and image blocks; and stored XSS in the comments-pagination blocks (Alex Concha). Separately, unpublished Customizer changesets could be discovered by unauthenticated users (Antonio Lorensius Silaban), and notes could be read by privileged users who lack edit access to the attached post. Two of the XSS reports were credited to Anthropic — AI-assisted vulnerability research is now showing up in WordPress core's release notes, the same force that drove the PHP2Shell emergency. The release also refreshes WordPress's bundled root certificates in the wake of the eMudhra CA revocations.

Stored XSS in core keeps earning CVE-sized consequences because it chains: we tracked Comment2Shell turning an anonymous comment XSS into server RCE, and Click2Shell in 7.1.1 abusing core update plumbing to force theme installs. Every one of these fixed issues is a block in someone else's chain.

What Should You Do?

  1. Update to 7.1.4 now — via Dashboard → Updates or automatic background updates; if you manage many sites, batch them this week rather than waiting for the December 7.2 cycle.
  2. Control the upgrade window — run updates during low-traffic windows, avoid leaving a site mid-upgrade, and confirm the update completed cleanly; the RCE fix protects the process you are about to run.
  3. Audit who can reach privileged endpoints — contributor-level users injecting crafted block markup or user logins is the delivery path for most of this batch; tighten roles and review recent user records for oddities.
  4. Re-check plugins and themes for the same sinks — core fixed its stored XSS reports, but the plugin ecosystem's upload and XSS flaws remain under active attack; extend the same scrutiny outward from core.

The WAF Angle

An RCE in the upgrade process is a governance problem that a WAF can only babysit. The control that matters is operational discipline: patch during windows you choose, monitor the upgrade endpoints during those windows, and let the WAF flag anything anomalous — unexpected writes, off-schedule update traffic, requests to update handlers outside maintenance periods — as the tripwire for the exact window this fix closes. For the stored XSS half of the release, the WAF contribution is input-shaping at scale: crafted block markup and login strings are exactly the kind of payload a well-tuned ruleset can strip or flag before they persist into the database, cutting the chain at its storage step before an admin ever renders it — the same blocking logic that made the 440,000-exploit-attempt waves against WordPress plugins survivable. Core patching closes the holes; edge filtering keeps the payloads from queuing up while every site on the internet catches up.

Sources