WordPress 7.1.4 Security Release: 22 Fixes, Update Now

WordPress 7.1.4 Security Release: 22 Fixes

WordPress 7.1.4 is a security release, and it’s a big one. Released on October 28, 2026, it fixes 22 vulnerabilities in WordPress core. One of them sits in the update process itself. WordPress’s recommendation is clear: update your sites immediately (official announcement).

Here’s what’s fixed, who is actually at risk, and what to check today.

 

What is WordPress 7.1.4?

WordPress 7.1.4 is a security release published on October 28, 2026. It addresses 22 security vulnerabilities, including:

  • a race condition in the core update process that could lead to remote code execution

  • multiple stored cross-site scripting (XSS) issues

  • an information disclosure flaw affecting unpublished Customizer changes

WordPress recommends updating immediately. The fixes were also backported to every older branch down to WordPress 4.7 (HelpHub).

 

The short version

  • What: 22 security vulnerabilities fixed in WordPress core. Patchstack counts them as 17 advisories.

  • Most serious: a race condition during updates that could lead to remote code execution. It needs no account, but the timing has to be exactly right.

  • Most fixes: stored XSS, mostly requiring a Contributor account or higher

  • Affected: practically every WordPress version still in use

  • To do: confirm every site runs 7.1.4 or the patched version of its branch, and block web access to wp-content/upgrade/

 

Which WordPress versions are affected?

According to the official HelpHub page, versions 7.0 and 6.9 are affected by all 22 vulnerabilities. Older versions are affected by fewer, but none of them is completely unaffected.

Your branchAffected byPatched version
7.1
all fixes
7.1.4
7.0
22 of 22
7.0.8
6.9
22 of 22
6.9.11
6.7 – 6.8
20 of 22
6.7.11 / 6.8.12
6.6
19 of 22
6.6.11
6.4 – 6.5
17 of 22
6.4.14 / 6.5.14
5.9 – 6.3
9 of 22
5.9.20 – 6.3.14
5.0 – 5.8
6 of 22
5.0.31 – 5.8.19
4.7 – 4.9
2–4 of 22
4.7.39 – 4.9.35
4.6 and older
–
no security updates
 

One honest note: WordPress backports these fixes as a courtesy. As the announcement puts it, only the most recent version is actively supported. A site on 6.4 is patched today, but it still misses everything else that has changed since. Also, WordPress says the backports “will ship as they become ready”, so packages for older branches may arrive with a delay.

 

What WordPress 7.1.4 fixes

WordPress doesn’t publish severity scores for these issues. The most useful question is therefore: what does an attacker need to exploit this? The requirements below come from the HelpHub list. Where HelpHub doesn’t name a role, they come from Patchstack’s analysis.

AreaProblemWhat an attacker needs
Core update process
Race condition that could lead to remote code execution
No account, but exact timing during an update and a web-reachable wp-content/upgrade/ folder*
Customizer
Unpublished Customizer changes visible to visitors
No account
Interactivity API
Multiple stored XSS issues (javascript: URLs, event handlers, prototype pollution), a denial-of-service issue, object elements loading admin pages
Contributor+
Interactivity Router
Stored XSS via uploaded text files
Author+
Block markup
Stored XSS via whitespace in block delimiters
Contributor+
Customizer selective refresh
Stored XSS
Contributor+
Categories, Comments Pagination, Post Navigation Link blocks
Stored XSS
Contributor+
Image and Playlist blocks
Hardening of unsafe replacements
Author+*
Script Modules
Post content could shadow Script Module data
Contributor+*
Personal data erasure requests
Stored XSS
Editor+
Notes
Custom roles that moderate comments could read, edit and delete notes on posts they can’t edit
Custom roles only
Multisite user screens
Hardening for unescaped usernames
Usernames created outside core*
Root certificates
Updated after the eMudhra revocation
–
*Requirement per Patchstack’s analysis, not stated in the official release notes.
 

The three fixes that matter most

1. Remote code execution during updates

The official release notes describe “a race condition during core updates that could lead to remote code execution.” They don’t detail how it can be exploited.

Patchstack’s analysis fills in the details. During an update, WordPress unpacks the package into wp-content/upgrade/, which the web server can serve like any other folder. Before 7.1.4, that folder’s name was predictable, and the file that blocks directory listing got deleted. For the few seconds an update runs, a complete copy of WordPress was reachable there, including its setup script.

That sounds dramatic, but the conditions matter. According to Patchstack, an attacker has to hit the exact window while an update runs, and the folder must be reachable over the web. Patchstack rates it as hard to exploit and would not call it practical. But it needs no account, and the window opens again with every update, including automatic ones. 7.1.4 makes the folder name random and keeps the protection file in place.

What to do: Update, and have your host or administrator block web access to wp-content/upgrade/ at the server level (see below).

2. Customizer changes visible to anyone

Unpublished Customizer changesets could be discovered by visitors who weren’t logged in. This is an information disclosure issue, not a site takeover. But if you were preparing a redesign, a campaign or new content in the Customizer, others could have seen it before you published it.

3. Stored XSS, many times over

Many of the fixes address stored cross-site scripting, seven of them in the Interactivity API alone (per Patchstack). The pattern is always the same. Someone with a Contributor account or higher saves specially crafted content. When another user opens that content, the malicious script runs in their browser, inside their logged-in session.

If that user is an administrator, the script can trigger actions in the admin area. It doesn’t get direct server access, but it can do whatever that session allows, as long as no other protection stops it.

That’s why these fixes matter most for sites with several users: guest authors, editorial teams, membership sites, or sites with open registration.

 

What to do now

  1. Check the version. Go to Dashboard → Updates and confirm 7.1.4, or the patched version of your branch. Automatic background updates handle most sites, but “auto-updates are on” isn’t the same as “this site is updated.”

  2. Updating manually? Block the folder first. The update to 7.1.4 still runs the old update mechanism one last time. Add the server rule below first, then update.

  3. Block wp-content/upgrade/ at the server. According to Patchstack, a security plugin can’t protect this folder, because the unpacked copy doesn’t load your plugins. The rule has to live in the server config or in the root .htaccess:

				
					# nginx (inside the server block)
location ^~ /wp-content/upgrade/ { deny all; }
				
			
				
					# Apache (root .htaccess, outside the "# BEGIN WordPress" block)
RedirectMatch 403 ^/wp-content/upgrade/
				
			
  1. Review user accounts. Who has Contributor, Author or Editor access? Remove accounts that are no longer needed, such as former freelancers, old agencies or test users.

  2. Check sites with open registration. If anyone can sign up and get a role that allows them to create content, this release matters most for you.

 

After the update: five quick checks

A routine core update is usually straightforward. Plugins, themes or custom code can still react to it, so we check these on every site after an update:

  • Version: Dashboard → Updates shows 7.1.4 (or your branch’s patched version), with no “update failed” notice.

  • Upgrade folder: Visit yourdomain.com/wp-content/upgrade/ in a browser. You should see “403 Forbidden”, not a file list.

  • Leftovers: If a .maintenance file is still in the site root, the update stopped halfway.

  • Editor and Customizer: Open a post in the block editor, then the Customizer if you use it. Custom blocks built on the Interactivity API deserve a closer look, because 7.1.4 tightens how it handles bindings.

  • WooCommerce: Place one test order covering cart, checkout, payment and order email. It takes two minutes.

Our full routine is in how to update WordPress without breaking your site. An update fixes vulnerabilities, but it doesn’t remove an infection that’s already there. If you see unknown users, strange redirects or changed files, follow our guide what to do if your WordPress site is hacked.

 

FAQ

Is WordPress 7.1.4 a mandatory security update?

WordPress recommends updating immediately. The release fixes 22 security vulnerabilities, including an issue in the core update process that could lead to remote code execution.

Which WordPress versions are affected?

It depends on the branch. WordPress 7.0 and 6.9 are affected by all 22 issues, older branches by fewer. Patched versions exist for every branch down to 4.7. Versions 4.6 and older receive no security updates.

Is my site safe if automatic updates are on?

Only once the update has actually finished. Check the installed version in your dashboard instead of assuming the background update worked.

Is updating WordPress enough to secure a website?

Updating core fixes the vulnerabilities in this release. It doesn’t replace plugin and theme updates, account reviews, backups, or server-level protection like blocking wp-content/upgrade/.

 

The fourth security release since September 17

7.1.4 is the fourth security release in the WordPress 7.1 series, after 7.1.1 (September 17), 7.1.2 (September 22) and 7.1.3 (October 6). In between came a critical PHP security release, which had to be fixed on the server, not in WordPress.

The fixes come from many places: independent researchers, the WordPress Security Team itself, and Anthropic, an AI company credited with two of the reports. For site owners, the takeaway isn’t that WordPress is unsafe. It’s that every release has to reach every site, and someone has to check that it did, on the same day. That’s exactly what a WordPress maintenance plan should cover.

Testing WordPress 7.2? Beta 3 was released at the same time and contains all applicable fixes. Our WordPress 7.2 Beta 2 overview covers what’s coming. As always: staging, never production.

Sources: WordPress 7.1.4 announcement · WordPress 7.1.4 HelpHub · Patchstack: WordPress 7.1.4 Security Release

Share this :

Leave a Reply