WordPress released version 7.1.4 on October 28, 2026, with security fixes spanning 17 advisories. For site owners tracking the WordPress 7.1.4 security release, the immediate step is to update, then check whether the web server exposes the upgrade directory during updates.
Patchstack counts 22 vulnerabilities in the release, including stored cross-site scripting issues, a notes-permissions flaw and an update-process race condition that can lead to remote code execution. Most reported issues require an account; the race condition is the exception that warrants a separate configuration check.
What the WordPress 7.1.4 security release fixes
The official release post describes fixes for multiple security issues and recommends updating sites immediately. Patchstack’s breakdown counts 22 vulnerabilities across 17 advisories, a larger set than the seven fixes it attributed to version 7.1.3 three weeks earlier. These figures come from Patchstack’s analysis; the official announcement does not state a total.
The fixes cover stored XSS in several parts of WordPress, including block markup, the Interactivity API, the Customizer and block labels. The release also addresses exposed unpublished Customizer changesets, access to notes without permission to edit their associated posts, and a hardening issue involving usernames on multisite Network Users screens.
Seven advisories involve the Interactivity API, according to Patchstack. The issues include unsafe bindings that could produce script execution, and one that could hang a visitor’s browser tab. Patchstack says the fixes change validation in KSES, the PHP directive processor and the client runtime.
The update-window flaw needs a server-side check
The most unusual issue is a race condition in WordPress’s upgrade process. Patchstack says an attacker without an account would have to reach a particular path during the brief period when an update is running, and the site’s wp-content/upgrade/ directory would need to be reachable over the web. Patchstack describes the window as very short and says it would not call the issue practical to exploit.
That qualification is not a reason to skip the update. WordPress lists the upgrade-process weakness among the security fixes in 7.1.4, and Patchstack says the window can recur during updates, including unattended ones. Its recommended additional check is to deny web access to wp-content/upgrade/ and make sure the directory cannot be listed.
Patchstack also notes that a PHP firewall cannot block this particular request because the extracted copy runs from its own files. That makes the web server’s directory-access rules relevant to this issue, alongside installing the patched release.
Update WordPress and check supported branches
The official WordPress 7.1.4 announcement, published October 28, recommends updating immediately. Sites with automatic background updates will begin the process automatically, while others can update from Dashboard → Updates or download the release from WordPress.org.
WordPress says the security fixes were backported to branches eligible for security fixes, through version 4.7. Patchstack lists the available backports as 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14 and versions down to 4.7.39. Patchstack says sites running 4.6 or older do not receive these fixes.
For a fleet of sites, check the installed branch and confirm the update completed rather than assuming background updates have finished. Then review access to the upgrade directory and the user roles on sites where Contributors or other lower-privilege accounts can add content.
Why developers should review roles and content paths
Most of the issues described by Patchstack begin with a logged-in account, often a Contributor or Author, and some require an Editor or administrator to open the affected screen or content. That does not mean every site has the same exposure: the required role and action vary by issue.
One example is the notes-permissions fix. Patchstack says it matters when a custom role, plugin or post type separates the moderate_comments capability from permission to edit the relevant post. WordPress now requires edit access to the post before a user can read, change or delete its notes.
Review custom roles and capability-granting plugins after updating, especially on sites that use editorial workflows beyond the default roles. The aim is to verify that the access model still matches the site’s needs, not to treat every listed issue as exploitable on every installation.
WordPress 7.1.4 security release FAQ
Should I install WordPress 7.1.4 now?
Yes. WordPress recommends immediate updates for this security release. If the site runs another supported branch, install the applicable backport listed for that branch.
Does the remote code execution issue require a WordPress account?
Patchstack says the upgrade-process race condition requires no account, but an attacker must reach the relevant path during the short update window, and the upgrade directory must be web-accessible. Patchstack recommends blocking web access to that directory as an additional measure.
Are older WordPress versions patched?
WordPress says fixes were backported to branches eligible for security fixes through 4.7. Patchstack says its listed backports reach 4.7.39 and that sites on 4.6 or older do not receive the fixes.
Update each site to the latest applicable security release, then verify that wp-content/upgrade/ is not publicly accessible or listable.