On this page (7 sections)
The WordPress project published WordPress 7.1.4 on October 28, 2026, as a security release covering multiple issues. According to the official WordPress.org announcement, the project recommends updating sites immediately.
If you run WordPress, whether as a business owner, agency or hosting administrator, this release applies to you. The announcement lists the fixes but gives no CVE identifiers or CVSS scores, so this article describes only what the project has stated.
What WordPress fixed in 7.1.4
The WordPress 7.1.4 announcement lists these security fixes. The wording below follows the project's descriptions; no further technical detail was published.
- A weakness in the WordPress upgrade process that can lead to remote code execution during the upgrade window (reported by Umut Bayram).
- A stored XSS using specially crafted block markup.
- Privacy Data Removal Requests that can be created in a way that leads to stored XSS.
- Multiple stored XSS issues in the Interactivity API, found independently by several researchers and members of the WordPress Security Team.
- A stored denial of service issue in the Interactivity API.
- A stored XSS in Customizer selective refresh.
- Stored XSS in the Categories block, in the Playlist and image blocks, and in the core/comments-pagination-next and core/comments-pagination-previous blocks.
- Specially crafted user logins that can lead to a stored XSS.
- Unpublished customizer changesets that can be discovered by unauthenticated users.
- Notes that can be read by privileged users who lack access to edit the post the note is attached to.
- An update to the bundled root certificates due to the eMudhra revocation.
Why these weakness types matter
Most items are stored cross-site scripting (XSS). In stored XSS, malicious script is saved in the site's data, such as block content, a username or a request record, and runs later in the browser of whoever views it. When the viewer is an administrator, that script can act with their permissions, for example by creating accounts or changing content. The announcement does not describe which privileges an attacker would need for each issue, so treat that as unknown.
The upgrade-process weakness is the most notable item because it is described as leading to remote code execution during the upgrade window. No exploit details or preconditions were published, and the research does not say whether it has been exploited. The practical lesson is to complete the update promptly and avoid leaving a site half-upgraded.
The unpublished changeset item is an information exposure: draft design changes could be seen by people who are not logged in. The notes item is a smaller exposure among users who already have elevated roles. The certificate change reflects the revocation of eMudhra roots, so the bundled trust store was updated.
Who is affected
Any WordPress site that has not applied 7.1.4 or a corresponding backport is potentially affected by the issues relevant to its branch. The project says security fixes are being backported to all branches eligible for security fixes, currently through 4.7, and that backports are in progress and will ship as they become ready. It also reminds users that only the most recent version of WordPress is actively supported.
Sites with many contributors, public comment forms, custom or third-party blocks, or use of the Interactivity API have more places where stored content is created, so they deserve priority. The research does not say which versions of the 7.x line are affected by each individual issue, so do not assume an older 7.x release is safe.
How to check your version
Run this WP-CLI command on the server, inside your site's directory. It prints the installed WordPress version; you want to see 7.1.4 or, on an older branch, the backport release once it ships.
wp core versionThis read-only command checks whether a core update is available for the site.
wp core check-updateYou can also open the Dashboard, go to Updates, and read the version shown at the top. If you manage many sites, compare versions across all of them, since automatic background updates only apply where they are supported and enabled.
What to do now
- Back up files and database, and confirm the backup can be restored.
- Open Dashboard, then Updates, and click Update Now to install WordPress 7.1.4, or confirm that the automatic background update has already run.
- Run wp core version on each site and confirm the result is 7.1.4 (or the backport for your branch when available).
- If you are on an older branch, watch the WordPress news page for your backport release, since backports ship as they become ready.
- Plan a move off any branch that no longer receives security fixes, because only the latest version is actively supported.
- Review administrator and editor accounts, and remove ones you do not recognize.
- Look for unexpected posts, comments, user logins with odd characters, or privacy request entries created before you updated.
- Update plugins and themes too, since block and Interactivity API code often comes from them.
If you find suspicious content or accounts created before the update, follow a clean-up process such as Website hacked: what to do and change administrator passwords.
Detection and monitoring afterwards
Nothing in the announcement says these issues were exploited, so absence of evidence should not be read as a clean bill of health. After updating, review recent content changes and user lists for anything unexpected. The guide on how to check if a website is hacked walks through the signs to look for.
Because this release also updates bundled root certificates, keep an eye on your own certificate health. The free SSL certificate checker shows what your site presents, and Webforta Monitor can alert you to certificate and header changes over time. A firewall can add a layer of filtering, but it does not replace updating core; see what is a WAF for what it can and cannot do.
Timeline
| Date | Event |
|---|---|
| 2026-10-28 | WordPress 7.1.4 security release announced |
| Ongoing | Backports to branches eligible for security fixes (currently through 4.7) ship as they become ready |
| 2026-12-08 | WordPress 7.2 planned; 7.2 Beta 3 already contains all applicable fixes |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
