
The WordPress 7.1.4 security update was released on 28 October 2026 and fixes 22 vulnerabilities, including a race condition in the core update process that could lead to remote code execution. Most of the other fixes are stored XSS flaws that need a Contributor account or higher. Everyone should update from Dashboard > Updates after a backup, then check that wp-content/upgrade/ is not reachable from the web.
WordPress shipped the WordPress 7.1.4 security update on 28 October, just three weeks after 7.1.3. The official announcement calls it a security release and says to update immediately. The release notes put the count at 22 vulnerabilities across 32 changed files, which makes it a much bigger patch than the seven fixes in 7.1.3.
None of the sources we read report active exploitation. Still, one fix touches the update process itself, and that one is worth understanding. Below we cover what changed, who is exposed, how to update, and a server check that a patch alone does not do for you.
What the WordPress 7.1.4 security update fixes
The release notes list 18 bullet points that together cover 22 vulnerabilities. Patchstack has grouped them by the access an attacker needs, which is the most useful way to read the list.
| Fix | Access needed to exploit |
|---|---|
| Race condition during core updates (remote code execution) | None, but only during the few seconds an update runs |
| Unpublished Customizer changesets visible to visitors | None |
| Stored XSS in the Interactivity API, Customizer selective refresh, Categories block and comments pagination | Contributor or higher |
| Interactivity Router XSS through uploaded text files, plus Image and Playlist block hardening | Author or higher |
| Stored XSS on the personal data erasure screen | Editor or higher, plus an admin opening Tools > Erase Personal Data |
| Notes readable by roles that can moderate comments but not edit the post | A custom role or post type with that setup |
The release also updates the bundled root certificates after the eMudhra revocation. That is housekeeping, not a vulnerability fix. Credits in the announcement include Umut Bayram for the update-process flaw, and Anthropic for the XSS issues in Privacy Data Removal Requests and User Logins.
The update-process flaw: why it matters
This is the headline fix. WordPress unpacks new core files into a folder under wp-content/upgrade/ while it updates. Per Patchstack, an attacker with no account could request the right path during that short window while the folder is reachable over the web. Patchstack rates the attack complexity as high and does not consider it practical to exploit. The official announcement leaves out the technical detail on purpose.
The catch is that the window opens on every update, including the automatic ones that run while you sleep. According to Patchstack, the fix gives the extraction folder a random suffix, recreates its index.php and stops deleting that file. Patchstack also notes that a PHP-level firewall cannot block this request, so a web server rule is the only layer that helps.
Do not test this on someone else’s site. To check your own, open yourdomain.com/wp-content/upgrade/ in a browser. You want a 403 or 404, or at least a blank page. If you see a file listing, ask your host to block web access to that folder.
Who needs to worry about the stored XSS fixes
Most of the 22 fixes are stored cross-site scripting bugs. They need a logged-in user who can already write content, which means a single-author blog with one admin is far less exposed than a membership site or a store with many staff accounts. Our earlier WordPress 7.1.3 security update guide made the same point about roles.
The practical step is to look at Users > All Users and ask who really needs Contributor or higher. Remove dormant accounts and downgrade anyone who no longer writes. It costs ten minutes and shrinks the attack surface for this and future releases.
How to update to WordPress 7.1.4
WordPress says that on sites with automatic background updates, the process begins on its own. Confirm it rather than assume, because hosts and config settings can block it.
- Take a full backup of files and database. Your host’s backup tool or a backup plugin both work.
- Go to Dashboard > Updates. If you see an update to 7.1.4 (or the patched number for your branch), click Update Now.
- Wait for the process to finish, then open the front end and the Posts screen to confirm they load.
- Open
/wp-content/upgrade/on your domain and confirm it returns a 403, 404 or blank page. - Clear your page cache and CDN cache so visitors get fresh files.
If you are not on the newest branch, Patchstack lists backports for 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14 and 6.4.14, going down to 4.7.39. WordPress also states that only the latest version is actively supported and that 4.6 and earlier get no security updates. Plan a move to 7.1 when you can.
Running behind Cloudflare? A purge after the update is a good habit. Our Cloudflare free vs Pro comparison explains what the free plan does and does not protect, which matters here because a CDN firewall will not stop that upgrade-folder request either.
What 7.1.4 means for WordPress 7.2
The announcement says WordPress 7.2 Beta 3 includes the applicable fixes, and that 7.2 is planned for 8 December. If you test betas on a staging site, move to the latest beta. Production sites should stay on 7.1.4 until the final 7.2 release. If you missed the earlier patches in this run of releases, our write-ups of 7.1.2 and the PHP2Shell vulnerability cover the background.
Post-update checklist
| Check | Where | Why |
|---|---|---|
| Version shows 7.1.4 or your branch’s patched number | Dashboard > Updates | Confirms the patch landed |
| Upgrade folder returns 403, 404 or blank | Browser, /wp-content/upgrade/ |
Closes the window the RCE fix targets |
| Review Contributor and higher accounts | Users > All Users | Most XSS fixes need one of these roles |
| Test a post edit and an image upload | Posts and Media | Confirms editing still works |
| Clear page, CDN and object caches | Cache plugin and Cloudflare | Serves updated files |
Back up, update to WordPress 7.1.4 today, confirm the version in Dashboard > Updates, and make sure wp-content/upgrade/ is blocked on your server. Then trim the list of Contributor and higher accounts. We found no report of active exploitation, but 22 fixes in one release is reason enough not to wait.
Frequently asked questions
Is WordPress 7.1.4 a security release?
Yes. The announcement calls it a security release and recommends updating immediately. The release notes cover 22 vulnerabilities.
Will WordPress 7.1.4 install automatically?
On sites that support automatic background updates, WordPress says the update will begin automatically. Check Dashboard > Updates to be sure.
Is the remote code execution flaw being exploited?
Patchstack does not report any active exploitation. It also rates the attack complexity as high, because it depends on a request landing during the few seconds an update runs.
Do I need to update if I am the only user on my site?
Yes. Even if the XSS fixes need roles you do not use, the update-process fix applies to every site, and the project recommends updating immediately.
What if I am on an older WordPress branch?
Fixes are being backported to every branch eligible for security updates, back to 4.7, and they ship as each is ready. WordPress 4.6 and earlier no longer receive security updates.
Sources: WordPress.org: WordPress 7.1.4; WordPress.org: Version 7.1.4 release notes; Patchstack: WordPress 7.1.4 security release; Search Engine Journal: WordPress announces another security release. Checked October 2026.


