WordPress 7.2 Beta 1 is out for testing as PHP security warnings intensify for site owners.

23 October 2026

WordPress 7.2 Beta 1 is ready for download and testing as of October 20, 2026, marking the start of the beta cycle for the major release. Beta 2 and 3 are scheduled for October 27 and November 3, with Beta 4 slated for November 10. The final release candidate, RC1, is due November 17, ahead of the December 8 launch.

Six key reasons to test WordPress 7.2

1. Fresh core contributions: This release introduces over five dozen new enhancements and fixes, all contributed and reviewed by volunteers. From performance optimizations to coding standards and language improvements - there's a lot to check.

2. Plugin Compatibility Check: Older code that powers countless plugins and themes may no longer function properly with upcoming mechanical changes to new WordPress core.

3. Core Markup Access: The latest default template, Twenty Twenty-Eight, includes modern accessibility features. Testers can check out the full accessibility-ready markup for spotless functionality.

4. Gutenberg Plugins: New blocks get developer attention in each major release. Testers can keep an eye out for enhancements and potential issues in popular Gutenberg plugins.

5. WordCamp Videos: Incorporate WordCamp videos seamlessly into your posts. This release enables embedding WordCamp event videos using a block.

WordPress 7.2 beta testing tips

- Set up a staging site: Plug in the beta, give it a complete workout, and undo it all with one click.

- Fork your site: A perfect demo - copy tie down, clone production. It works, too.

- Install locally: Just blow it away for full testing. Testers can clone the directory to your local environment, plus extra tweaking.

- Turn on beta testing notifications: Follow up. Responses. Keep your priorities top of mind with a next display on your WordPress Plugins page.

Beta 1 kicks off a month of testing, with releases of Beta 2 (October 27), Beta 3 (November 3), and Beta 4 (November 10) following the standard cycle. The final release candidate slated for November 17, RC1, will enable final checks before WordPress 7.2 launches to over 89 million sites on December 8.

Here's why this matters

Initially, WordPress 7.2 got attention for the last major CLI version, a performance refresh, and a code quality boost. But until now, no one talked about what happens after launch.

This release delivers crucial security fixes for PHP, the backbone of WordPress. Reports indicate over 3 million WordPress sites might fail under the new update without addressing existing vulnerabilities.

More on this is available via Top 5 Mobile Casinos Worth Trying.

Visit the WordPress forums, events schedule, or handbook on how to contribute to the WordPress project through November.

PHP security warning details

The WordPress project updated its security recommendations following major vulnerabilities discovered in PHP this month. On October 20, 2026, fixes were released for PHP 8.2 and later. Users of older versions should consider taking their system offline while waiting for patches.

After reviewing recommendations from cybersecurity experts, WordPress issued these suggestions for site owners:

If you can't immediately apply the latest PHP patches, consider taking the server offline. If you use a PHP version no longer receiving security updates, you should take your server offline and update immediately.

Next steps for site owners

1. Check current PHP version: Visit Tools > Site Health > Info to find your site's PHP version. The recommended minimum version is 8.2.

2. Consider offline hosting: If running an older PHP version with self-managed hosting, work with your provider to confirm patching status.

3. For WordPress maintainers: Update to the latest WordPress version (6.5.11 fixes several security issues) before checking your PHP configuration.

4. Confirm your update status: All WordPress users should verify their installation, regardless of other factors. Some environments might miss automated security updates.

The WordPress Test Team encourages users to focus on beta testing separately from PHP security concerns. The beta cycle primarily examines usability improvements and plugin compatibility.

Site administrators should prioritize communication with hosting providers about PHP updates. WordPress cannot resolve server-level vulnerabilities - potential impacts depend on the latest downstream changes.

By addressing these concerns separately, testers can manage issues through staging, backups, and host communications during the 7.2 beta period.