WordPress 7.2 Beta 3: Shipped With the 7.1.4 Security Release

WordPress 7.2 Beta 3 came out on October 28, 2026, a week earlier than planned. It didn’t get its own announcement. It shipped alongside WordPress 7.1.4, a security release, and carries the same fixes. If you only do one thing after reading this, update your live sites to 7.1.4.

This post covers what WordPress 7.2 Beta 3 means for live sites and test sites. For the developer changes that came just before it, read what changed in Beta 2. For the bigger picture, see my WordPress 7.2 release guide.

Why did WordPress 7.2 Beta 3 ship with 7.1.4?

When core ships a security release in the middle of a beta cycle, the beta needs the same fixes. The 7.1.4 announcement says Beta 3 was released at the same time, “containing all applicable fixes.” The Beta 4 announcement a week later confirmed it under the heading “Wait, what happened to 7.2 Beta 3???”

So Beta 3 is Beta 2 plus the 7.1.4 security fixes, released on the security release’s schedule instead of the beta schedule.

What does WordPress 7.1.4 fix?

7.1.4 fixes several security issues. The announcement recommends updating right away. The list:

• A weakness in the upgrade process that could allow remote code execution while an upgrade is running.
• Several stored cross-site scripting (XSS) issues, including in block markup, Customizer selective refresh, the Categories, Playlist and Image blocks, the comments pagination blocks and the Interactivity API.
• A stored denial-of-service issue in the Interactivity API.
• Stored XSS through privacy data removal requests.
• Unpublished Customizer changesets that visitors who weren’t logged in could see.
• Notes that users without edit access could read.
• An updated root certificate bundle, after the eMudhra certificate revocation.

The fixes were also backported to every older branch that still gets security updates, back to WordPress 4.7.

Should you update live sites?

Yes, to 7.1.4. Not to the beta. Most sites get minor releases through automatic background updates, but check Dashboard → Updates on each site to confirm. If you manage client sites, this is the one to check today.

What should developers test in WordPress 7.2 Beta 3?

Beta 3 doesn’t add new features, so re-run your Beta 2 checks. Then spend extra time on the areas the security fixes touched, because that’s where a behavior change is most likely to show up:

• Custom blocks that output markup. Check your saved and dynamic block output still renders as expected.
• Customizer selective refresh. If your theme uses partials, confirm they still refresh.
• Interactivity API stores. Test any interactive blocks, especially ones that render user content.
• Comments and pagination. Test themes that customize the comments pagination blocks.
• Privacy tools. If a plugin hooks into data removal requests, run one end to end.

WordPress 7.2 release schedule

Beta 3 moved, and two milestones were added. Here’s the current schedule:

What came after Beta 3?

Beta 4 came out on November 3, 2026, with accessibility, editor reliability and developer API fixes. Highlights:

• Better keyboard focus in Windows High Contrast mode (Trac #45910).
• Fixes for right-to-left (RTL) block alignment and custom block spacing.
• Fixes for revision handling, input validation and compatibility.
• Refinements to Ipsum, the new default theme: focus indicators, screen reader links, RTL, block patterns, touch target spacing and palette compatibility (Trac #66352).
• Translation updates now show individually on the Updates screen (Trac #42281).

Beta 5 is scheduled for November 10, and Release Candidate 1 follows on November 17.

How do I test the latest beta?

Beta 3 has been replaced by newer betas, so install the latest one on a staging or local site with a fresh backup. With WP-CLI:

wp core update --version=7.2-beta4

You can also use the WordPress Beta Tester plugin (Bleeding edge channel, Beta/RC Only stream) or WordPress Playground. Found a bug? Report core issues on WordPress Trac and editor issues in the Gutenberg GitHub repository.

WordPress 7.2 Beta 3 FAQ

Before December 8

Update live sites to 7.1.4 first, then keep testing 7.2 on staging. My WordPress release tracker follows 7.2 through release day, and it has the free 30-check checklist I run on client sites before every major update.

Sources

This roundup is based on the official WordPress 7.1.4 and 7.2 Beta 4 announcements and the Make Core schedule.

• WordPress 7.1.4 (WordPress News)
• WordPress 7.2 Beta 4 (WordPress News)
• WordPress 7.2 (Make Core)
• WordPress 7.2 Release Party Schedule (Make Core)