Where WordPress 7.2 stands this week
WordPress 7.2 reached Release Candidate 1 on November 17, 2026. The final release is scheduled for December 8, 2026. The announcement says RC1 is “still under development” and should not run on production or mission-critical sites. The 7.2 field guide, published November 20, counts more than 440 Core Trac tickets in the release, over 260 of them bug fixes, plus the editor work from Gutenberg 23.7 through 24.3.
A day after RC1 the project shipped WordPress 7.1.5, a security release for the current stable version. Store teams should deal with that one before they think about 7.2.
WordPress 7.1.5 is the update to apply now
The 7.1.5 post lists 20 items. Most are vulnerability fixes. They include a multisite privilege escalation from Administrator to Super Admin, several cross-site scripting and SQL injection issues, an unauthenticated denial of service through XML-RPC pingbacks, and an unauthenticated privilege escalation through Template Part block attributes that the post says “could lead to remote code execution.” The project recommends updating immediately. The fixes are being backported to every branch still eligible for security fixes, currently back to 4.7, and the post says those backports will ship as they become ready.
Sites with automatic background updates will receive 7.1.5 on their own. Many WooCommerce stores turn off core auto-updates so they control timing, and those stores need someone to apply it by hand. We would check the version number in the dashboard of every store today instead of assuming the host has done it.
What changes in the admin and editor
Most of 7.2 is editor and admin work. From the Beta 1 announcement and the field guide, these are the changes a store team will notice:
- The admin menu and admin bar replace Dashicons with SVG icons from the WordPress icon library.
- Images can be resized, compressed and converted in the browser before upload. The field guide says this works in Chrome and Edge 137 or later on devices with more than 2 GB of memory, while Firefox and Safari fall back to server-side processing.
- The admin loads scripts and stylesheets as individual files for better browser caching, and prefetches resources for the screen you are likely to open next.
- Gallery settings gain responsive controls for columns, cropping and aspect ratios, and blocks gain text shadow controls.
- A new “On This Day” dashboard widget shows posts published on the same date in earlier years.
The Beta 1 post says browser-side image processing may reduce server load on hosts with limited image processing. For a catalog team that uploads hundreds of product photos a week, we would compare output quality and file sizes on staging first. The result now depends on which browser each person uses, so two people uploading the same photo may get different files.
Developer changes to test on a store
The developer notes are where plugins and custom themes are most likely to break. These are the ones we would test first on a WooCommerce site:
- jQuery Migrate moves to 3.6.0. The jQuery 4 preparation note says an update to the latest jQuery is “tentatively planned for WordPress 7.3,” and that Migrate is planned to be disabled by default around the end of 2027. Older checkout scripts, product sliders and admin screens built on jQuery may start logging warnings in the browser console.
- The
NO_BACKSLASH_ESCAPESSQL mode is now off by default. The field guide says sites can turn it back on with adb.phpdrop-in, and warns that this may cause compatibility issues. Custom SQL in reporting or ERP export code is worth a test run. - Custom admin color schemes and CSS that targets Dashicons pseudo-elements in the menu may need updates for the SVG icons.
- In the REST API, revision and autosave responses include only metadata registered for revisions, the comments
statusparameter is now an array, and a newrest_allowed_cors_methodsfilter controls theAccess-Control-Allow-Methodsheader.
One feature announced in Beta 1 will not ship. The Secrets API dev note was updated on November 17 to say the API “will no longer be shipping with WordPress 7.2.” It would have given plugins a standard, encrypted place to store credentials such as payment gateway keys, and the comments on the note show core contributors disagreed about shipping it. If a developer started building against wp_set_secret() or wp_get_secret() during the beta, that code needs a check for whether the functions exist, or it should wait.
How we would roll out 7.2
Install RC1 on a staging copy of the store now, using the WordPress Beta Tester plugin or WP-CLI with wp core update --version=7.2-RC1, as the RC1 post describes. Run checkout with each payment method, open the order and product edit screens, upload a few product images, and watch the browser console for jQuery Migrate warnings.
Then check your plugins. The WooCommerce 11.3 readme says “Tested up to: 7.1.” We would wait until WooCommerce and your payment plugin declare 7.2 support before updating production. For many stores December 8 falls inside a holiday change freeze. In that case, keep 7.1.5 and any later 7.1 security releases in place, and schedule 7.2 for the first maintenance window in January.





