Three separate patches landed this week, and they sit in three different places: WordPress core, PHP, and NGINX. WordPress 7.2 reached its first release candidate, and one planned feature did not make it. Outside core, a payments platform with WordPress roots announced its shutdown.

Security: One update for you, two for your host

WordPress 7.1.5 fixes 20 security issues, including SQL injection and a flaw that could lead to code execution. Sites with automatic background updates should already have it. If yours does not, update now.

The other two fixes are not yours to install. PHP’s November release fixes 18 flaws, seven of them critical. Two critical NGINX HTTP/2 flaws can let attackers run code on a server. WordPress updates do not touch either one. Ask your host which PHP and NGINX versions they run, and whether the fixed versions are installed.

This follows last week’s critical Apache HTTP/2 flaw. Web server software is having a rough month, and the patching sits with your hosting company, not with you.

WordPress Core: 7.2 RC1 arrives without the Secrets API

WordPress 7.2 Release Candidate 1 is ready for testing, with the final release set for December 8. Try it on a staging site, never on your live one.

The release candidate ships without the Secrets API. Core committer Peter Wilson reverted it on Monday. He wrote that feedback raised questions about the design. He added that a review found the new capabilities were not checked when secrets were set. The API would have given WordPress its first built-in way to store credentials such as API keys in encrypted form. Contributor Eric Mann, who led the work, said he will target WordPress 7.3.

For now, credentials that plugins store in your database stay as plain text, as before. That makes host-level and plugin-level protection more important, not less.

Two other WordPress.org projects shipped this week. Reprint copies your site’s files and database to a new host or a test copy, with no backup archive needed first. Try it on a test site first. A new free SMTP plugin fixes a quiet failure: some hosts block PHP’s mail() function, so password resets never arrive. Send yourself a reset email to check your site.

WordPress also proposed rules for dashboard banners. Plugins would declare why they show an admin notice, so promotional ones can be limited. Feedback is open until November 30.

One more browser change is worth knowing about. Chrome 158 rolled out on November 17 and dropped support for client-side XSLT. WordPress and several SEO plugins use XSLT to style XML sitemaps. In Chrome, your sitemap now looks like raw code. Search engines read the raw XML anyway, so rankings and indexing are not affected. WordPress 7.2 removes its sitemap stylesheet, and Yoast SEO is moving to CSS styling.

Business: Lemon Squeezy is closing

Lemon Squeezy, a payments platform founded by WordPress veterans and bought by Stripe in 2024, announced it is winding down. It closed new store sign-ups on November 16 and will stop processing payments on March 31, 2027. The deadline will not be extended.

Stripe wants merchants to move to its Managed Payments product. That product is not available in every country Lemon Squeezy supports, and it does not cover digital fulfillment or storefronts. Migration tooling arrives December 2. If you sell through Lemon Squeezy, export your customer, order, and subscription data now and start planning.

Commerce: Your checkout may already serve robots

AI shopping agents can already check out on WooCommerce stores that take cards. Whether that is good news depends on your store. Review your guest checkout settings, your live payment methods, and your CAPTCHA setup so you know who is buying.

Block Editor: Gutenberg 24.4

Gutenberg 24.4 adds note search and status filters. It also shows which blocks override your Global Styles and protects drafts. Test it on staging first.


End of article