WordPress released version 7.1.4 on October 28, 2026, fixing security weaknesses that include a flaw in the core upgrade process. In the release announcement, Aaron Jorbin recommends updating sites immediately.

Independent coverage from Patchstack's Dave Jong describes 22 vulnerabilities across 17 advisories. Dr. Web's Markus Seyfferth also reports the security release and the update-process weakness. For owners, the immediate task is to install the appropriate release and confirm the version actually running.

The release documentation also lists older-branch patches as released; those courtesy fixes carry a different support status.

A Weakness During Core Updates

The release documentation describes a race condition during core updates that could allow remote code execution. A race condition means the outcome depends on the timing of overlapping operations; here, the vulnerable period occurs while WordPress is being upgraded.

Patchstack says the weakness requires no account, but exploitation needs a brief update window and a web-accessible upgrade directory. The security company considers exploitation impractical because of that short window. Those conditions make timing and configuration relevant to the risk.

Complete the security update promptly. Use the timing and configuration requirements to understand the weakness when planning maintenance, while treating installation of the security release as the priority.

Other Fixes Cover Scripts And Permissions

WordPress's documentation also lists stored cross-site scripting fixes involving block delimiters, personal-data erasure requests, Customizer selective refresh, and Interactivity API features. Several require Contributor-level or higher access. Stored cross-site scripting involves malicious script content being saved and later executed in a browser.

Other fixes prevent unauthenticated access to unpublished Customizer changes and stop custom roles from reading, editing, or deleting notes on posts they cannot edit. Account permissions therefore matter alongside the upgrade-process issue; owners should consider the whole patch set when prioritizing installation.

The announcement also reports updated bundled root certificates following the eMudhra revocation, plus WordPress 7.2 Beta 3 with applicable fixes.

Older Branches Receive Courtesy Backports

The announcement says only the most recent WordPress version is actively supported. Security fixes for older branches are courtesy backports, extending through branch 4.7; their rollout was still progressing when the announcement appeared.

Dr. Web's October 28 report said that, at 19:30 German time, backports through branch 6.6 were available while older branches remained pending.

The release documentation lists backports as released, including 7.0.8, 6.9.11, 6.8.12, and versions extending through 4.7.39. It also says WordPress 4.6 and earlier receive no security updates. An older branch can receive a security patch without becoming actively supported.

For a site remaining on an older branch, separate the immediate patching task from the decision about moving to the supported release.

Check The Version After Updating

WordPress directs administrators to Dashboard > Updates > Update Now. Its announcement says sites supporting automatic background updates will begin updating automatically. For site owners, the sensible completion check is the installed version, regardless of whether the update was started manually or automatically.

The Dashboard documentation explains that the At a Glance widget displays the WordPress version. Use that readout after the update to confirm 7.1.4, or compare an older branch's version with the corresponding backport listed in the release documentation.

For anyone maintaining several sites, record the installed version for each one after its update. This creates a concrete completion list instead of treating a scheduled maintenance window as proof of installation. Keep the branch number alongside the patch number so older backports are not mistaken for 7.1.4.

Sources And Reporting

As part of our technology coverage, this report follows our source and correction standards, attributing release details to WordPress and distinguishing them from Patchstack's technical analysis and Dr. Web's rollout reporting.

Image: AI-generated image.