WordPress core

WordPress 7.1.4 security release

WordPress 7.1.4 is a short-cycle security release. Update sites now. Older branches got the same fixes, through 4.7. PHP2Shell is a separate PHP update.

What happened

WordPress 7.1.4 is a short-cycle security release. It fixes multiple issues. WordPress says to update sites immediately. Sites that already use automatic background updates should start on their own. The next major release, 7.2, is planned for December 8.

There is a weakness in the WordPress upgrade process that can lead to remote code execution during the upgrade window. Update anyway. Do it from Dashboard, Updates, then confirm the version finished on 7.1.4. Do not leave a site sitting on the update screen.

Most of the rest are stored cross-site scripting. They cover crafted block markup, the Interactivity API, Customizer selective refresh, the Categories block, Playlist and image blocks, comment pagination blocks, privacy data-removal requests, and specially crafted user logins. There is also a stored denial-of-service issue in the Interactivity API. Unpublished Customizer changesets could be discovered without logging in. Notes could be read by privileged users who cannot edit the post the note is attached to. Bundled root certificates were updated because of the eMudhra revocation.

The same fixes also shipped for older branches that still get security updates, through 4.7. That means 7.0.8, 6.9.11, 6.8.12, and matching releases down to 4.7.39. Only the newest WordPress version is actively supported. WordPress 7.2 Beta includes the applicable fixes. Do not install a beta on a live site.

Updating WordPress does not patch PHP2Shell (CVE-2026-109618 and CVE-2026-109619). If the server PHP version is still behind 8.5.12, 8.4.27, 8.3.36, or 8.2.35, update PHP too. See the PHP2Shell warning.

Who is affected

Any WordPress site that is not yet on 7.1.4, or on the matching security release for its branch.

Fixed version: 7.1.4, or the matching security release for your branch (7.0.8, 6.9.11, 6.8.12, and matching releases down to 4.7.39).

Do this now

  1. Open Dashboard, Updates, and click Update Now. If auto-updates are on, wait for them, then confirm the version.
  2. Check the version is 7.1.4, or the matching security release for your branch (for example 7.0.8, 6.9.11, or 6.8.12). A generic "you have the latest" line is not the check.
  3. On older branches, confirm the backport version number. Sites that skipped auto-updates may still be one release behind.
  4. Still update PHP for PHP2Shell. A WordPress update does not fix that. See the PHP2Shell warning.

Source: WordPress 7.1.4 security release

You patched it. Now watch the site.

Pro adds a cloud firewall, malware scanning, and login protection. 14 days. Card or PayPal, not charged today.

Start 14-day Pro trial

Larger screenshot

Enlarged image