Get your first month Premium free, use code PG_PRO at checkout

    Back to Blog
    Wordpress
    Security
    Nov 16, 20264 min readViktor Kiss

    WordPress 7.1.4: What Site Owners Need to Know

    WordPress 7.1.4: What Site Owners Need to Know

    WordPress 7.1.4 is a short-cycle security release released on October 28, 2026. It addresses multiple security issues, so site owners should prioritize updating their WordPress installations.

    What WordPress 7.1.4 fixes

    The release includes fixes for:

    • A weakness in the WordPress upgrade process that could lead to remote code execution during the upgrade window.
    • Multiple stored cross-site scripting (XSS) issues involving blocks, the Interactivity API, Customizer selective refresh, user logins, and other WordPress features.
    • A stored denial-of-service issue in the Interactivity API.
    • A privacy issue allowing unauthenticated users to discover unpublished Customizer changesets.
    • An issue where privileged users could read notes attached to posts they could not edit.
    • An update to bundled root certificates following the eMudhra revocation.

    The upgrade-window weakness is covered in a separate BitNinja post on requests to the WordPress upgrade directory: https://bitninja.com/blog/waf-rules-pie-register-ultimate-member-wp-upgrade/

    How to update

    You can update from the WordPress Dashboard:

    1. Open Updates.
    2. Select Update Now.

    WordPress 7.1.4 is also available from WordPress.org.

    Who is updated automatically

    WordPress has shipped with automatic updates turned on for minor core releases since WordPress 3.7. That setting covers maintenance releases and security releases. It does not, by itself, cover the next major version. WordPress 7.1.4 is a security release on the 7.1 branch, so it falls under the default. On a site where this is still enabled, and the site can apply background updates, WordPress starts the update on its own. In principle, those sites are protected by this release without anyone clicking Update Now. Plugins and themes are outside that default. Whether to turn auto-update on for them is covered here: https://phantomguard.io/blog/auto-update-for-wordpress-plugins-and-themes

    That is worth checking, not assuming. The setting can be on while the update still does not run: scheduled tasks may not be firing, WordPress may be unable to write its own files, the installation may be under version control, or the host may have turned WordPress’s updater off and update core on its own schedule. The version shown under Dashboard → Updates is the check that matters. It should read 7.1.4, or the security release for the older branch the site is actually running. A site on an older supported branch does not jump to 7.1.4. It receives the backport for that branch, which is the same kind of minor security update and follows the same default.

    Sites that have turned automatic minor and security updates off do not receive this release in the background. They should be updated manually now. Once a WordPress security release is public, the code changes are public with it, and scanning for unpatched sites usually picks up in the first days. Waiting means staying exposed through the period when that attention is highest. Outdated WordPress core is a common factor when sites are compromised: https://phantomguard.io/blog/why-wordpress-sites-get-hacked

    What to do next

    Install 7.1.4 now, or the security release for the branch the site is on. WordPress 7.2 is a major release, planned for December 8, 2026. These fixes should already be on the live site by the time that major release ships.

    This release updates WordPress core. Plugins and themes need their own updates in the same pass. An old plugin or theme can still expose a site after the core version is current.

    Seven recent cases are in this BitNinja post: https://bitninja.com/blog/7-new-vulnerabilities-blocked-by-bitninja/

    Branches older than 4.7 no longer receive security fixes. A site still on 4.6 or earlier is outside that support. It needs a planned upgrade to 7.1.4. Take a backup before that move.

    Why this matters for site security

    Security updates address weaknesses in WordPress core before they can create unnecessary risk for sites and their users. Keeping core current is an important part of maintaining a secure WordPress site, alongside managing updates for plugins and themes.

    Only the most recent WordPress version is actively supported. Security fixes are also being backported to eligible branches, currently through version 4.7, as they become ready. However, WordPress recommends updating to 7.1.4 immediately.

    Reference:

    https://wordpress.org/news/2026/10/wordpress-7-1-4/