Skip to content
← Back to Blog

WordPress 7.1.4 Fixes a Flaw in the Update Process Itself. Here Is How to Update Without Leaving the Door Open.

The most serious fix in WordPress 7.1.4 is in the update process itself. What it fixes, why the update window matters, and how to update every copy of your site safely.

On October 28, WordPress released version 7.1.4, a security release covering more than a dozen issues. Most security releases are routine: update, confirm, move on. This one has a twist worth understanding before you click the button. The most serious fix is for a weakness in the WordPress upgrade process itself.

WordPress describes it as a weakness that can lead to remote code execution during the upgrade window. In plain terms, the few moments when a site is unpacking and installing an update are the moments an attacker could use. That does not mean you should wait. It means the update deserves a plan rather than a reflex.

Where this comes from. The WordPress 7.1.4 release announcement and its HelpHub page on WordPress.org, read directly. We have not relied on third-party severity scores, which vary for this release.

What 7.1.4 Fixes

The release lists thirteen security items. Three matter most for association and nonprofit sites.

  • The upgrade process. The weakness described above, which affects the act of updating rather than any one feature.
  • Member logins and privacy requests. Two separate stored cross-site scripting issues: one through specially crafted user logins, one through privacy data removal requests. Most association sites have both, because members have accounts and privacy laws require a way to ask for data removal.
  • Content blocks. Stored cross-site scripting in several core blocks and in the Interactivity API, plus an issue that let unauthenticated visitors discover unpublished Customizer changes.

Stored cross-site scripting means someone saves malicious code into your site that later runs in another person's browser. When that browser belongs to an administrator, the attacker can act with that administrator's access.

Why the Update Window Matters

Most organizations think of an update as instant. It is not. WordPress downloads the package, unpacks it into a working folder on the server, and then copies the new files into place. On a busy or slow server that can take long enough to matter.

WordPress has not published technical details of the weakness, and that is normal for a fresh security release. So we will not guess at the mechanics. What the announcement does tell you is enough to act on: the risk sits in the update itself, so how and when you update is part of the fix.

How to Update Safely This Week

  • Take a fresh backup first. Database and files, stored somewhere other than the server being updated. You want a clean restore point dated before the update.
  • Update in a quiet window. Choose a time with low traffic and nobody publishing. Shorter, calmer updates leave less room for anything to go wrong.
  • Update every copy, not just the live site. Staging, development and any old copy still reachable on the internet all run the same code. Attackers do not care which one is the official site.
  • Confirm the version afterward. Look at the version number in the dashboard footer or the Updates screen. Do not assume an automatic update ran. Check that it did.
  • Check for strangers. After updating, review the user list for administrator accounts nobody recognizes, and the plugin list for anything nobody installed.

If You Are on a Managed Host

Many association sites run on hosts that control core updates, such as Pantheon, WP Engine or a similar platform. On those platforms you may not see an Update button at all. Updates arrive through the host's own process and still have to be applied and deployed to each environment. On some platforms, applying an update to development does not move it to the live site. Someone has to promote it.

Ask your host or developer one direct question: which WordPress version is the live site running right now? If the answer is anything below 7.1.4, ask when it will be updated, and get the answer in writing.

If You Are on an Older Version of WordPress

WordPress says the fixes are being backported to every older branch still eligible for security fixes, back to version 4.7, and that those backports will ship as they become ready. Two things follow from that. A site on an older branch may be waiting for its fix even now. And WordPress is clear that only the most recent version is actively supported. If your site is several major versions behind, this release is a good reason to plan the move forward rather than rely on backports.

One More Date to Know

WordPress 7.2 is currently planned for December 8. That is a major release, not a security patch, and major releases deserve testing on a staging copy before they reach the live site. Getting onto 7.1.4 now puts you in a clean position to test 7.2 when it arrives.

If You Do One Thing This Week

Find out which WordPress version every copy of your site is running, live and staging alike. If any of them is below 7.1.4, schedule the update with a backup in hand, and confirm the version afterward.

Send us your site address and we will tell you which WordPress version you are running and what it would take to get current safely.

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article Your Plan Assumes Non-Dues Revenue. Your Website Does Not.