The WordPress 7.1.4 security update was released on 28 October 2026. WordPress.org's release notes list fixes for 22 vulnerabilities, and Patchstack's analysis groups them into 17 advisories. For comparison, Patchstack notes that 7.1.3, three weeks earlier, had seven.

Most of the issues need a logged-in account to exploit. One does not. That one, plus the long list of Contributor-level issues, shapes what you should do beyond clicking "Update Now".

What Is in WordPress 7.1.4?

The WordPress.org release documentation credits each fix to the person who reported it. Grouped by theme, the release includes:

Stack of glowing content blocks with red sparks hidden inside two of them, representing stored XSS in WordPress blocks
Most fixes close ways for a low-privilege user to hide script inside content that someone else later views.

Which WordPress Versions Are Fixed?

As a courtesy, the fixes were backported to older branches on the same day. Only the newest 7.1 release is actively supported, so backports are a safety net rather than a long-term plan.

Table of patched WordPress versions by branch: 7.1.4, 7.0.8, 6.9.11, 6.8.12 and older branches down to 4.7.39
Find your branch, then confirm you are on at least the listed version.
BranchPatched versionIssues that apply
7.17.1.4All 22
7.07.0.8All 22
6.96.9.11All 22
6.86.8.1220 of 22
6.76.7.1120 of 22
6.66.6.1119 of 22
6.5 and 6.46.5.14 and 6.4.1417 of 22
4.74.7.392 of 22
4.6 and earlierNo updateNo longer receive security updates

Branches between 4.8 and 6.3 also received backports. The full list is in the WordPress.org release documentation linked below.

Which of the 22 Issues Matters Most?

For most site owners, it is the race condition during core updates, because it is the one that needs no account.

Patchstack explains the mechanism. When WordPress installs or updates something, it extracts the package into wp-content/upgrade/. Before 7.1.4, the folder name was predictable and the protective index.php was removed during clean-up. For the few seconds an update takes, a complete copy of WordPress could sit at a guessable, browsable path, including its setup script.

Update progress ring beside a briefly exposed folder with a red beam reaching into it, representing the update race condition
The window is only seconds long, but it opens on every update, including unattended ones.

WordPress 7.1.4 adds random characters to the folder name, keeps the index.php in place and stops wp-config.php being copied out of the working directory. Patchstack rated the attack as hard to pull off, but it also points out two things worth acting on:

On nginx, a rule like this does the job. Updates still work, because WordPress writes to that folder through the file system, not over the web.

location ^~ /wp-content/upgrade/ {
          deny all;
      }

On Apache or managed hosting, ask your host to apply the equivalent rule at server level.

Why Do Contributor Accounts Matter So Much This Time?

Patchstack's summary is blunt: almost everything in this release needs an account first, usually a Contributor. Several of the stored XSS issues let a Contributor save content that runs script when an editor, an administrator or a visitor loads it.

Four cards showing what access each WordPress 7.1.4 issue needs: no account, Contributor or Author, Editor, and custom roles
Account levels matter. Fewer people with Contributor access or above means less exposure.

That makes this a good moment for a quick role audit:

Stored XSS in an administrator's browser is exactly how the October Ninja Forms campaign planted hidden administrators. If anything looks off, my guide to finding hidden admin users in WordPress explains how to check from the database.

How Do I Update to WordPress 7.1.4 Safely?

For most sites, this is a routine minor update. A few minutes of preparation still pays off.

WordPress 7.1.4 update checklist: backup, update, confirm version, block upgrade folder, review roles, remove unknown accounts, test key journeys
A short, repeatable checklist for this and future security releases.
  1. Take a fresh backup of files and the database.
  2. Update from Dashboard → Updates → Update Now, or with WP-CLI.
  3. Confirm the version you are now running.
  4. Test the journeys that matter: forms, logins, checkout and any membership areas.
wp core update
      wp core version
      wp core verify-checksums

If you are deliberately staying on an older branch for now, wp core update --minor applies the security release for that branch without jumping to a new major version.

Check every site, not just the main one. Staging copies, old microsites and forgotten subdomains are often the ones still on an unpatched branch. They share the same risks and, sometimes, the same database credentials.

If an update ever leaves a site showing errors, my WordPress site down emergency checklist walks through the order to troubleshoot in.

What Should I Check After Updating?

Once 7.1.4 is installed, three quick checks are worth doing:

Frequently Asked Questions

Will my site update to 7.1.4 automatically?

If your site supports automatic background updates, WordPress says the update process will begin automatically. Many hosts and management tools also control this, so confirm the version rather than assuming it happened.

I am on WordPress 6.8. Do I have to jump to 7.1?

Not to get these fixes. WordPress released 6.8.12 with the fixes that apply to 6.8. Only the newest 7.1 branch is actively supported, though, so plan the move to 7.1 as part of normal maintenance.

Are any of these vulnerabilities being exploited?

The release notes do not mention exploitation. Patchstack described the upgrade race condition as needing very precise timing and not practical to exploit, but recommended blocking web access to the upgrade folder anyway. Update regardless.

Does a security plugin protect me instead?

Patchstack notes that a PHP-level firewall cannot block the upgrade race condition, because the extracted copy of WordPress does not load your site's plugins. Updating, and blocking the folder at the web server, are the reliable fixes.

Final Thoughts

WordPress 7.1.4 is a large security release, but the actions are simple. Update every site, confirm the version, block web access to the upgrade folder and take a few minutes to review who holds Contributor access and above.

Regular updates are far less stressful when they are part of a routine. My notes on what to include in a WordPress maintenance plan cover how to set one up, and my website maintenance service can take it off your plate entirely.

Official References

For the primary sources behind this article, and the latest updates, see: