WordPress 7.2 pushback, Contact Form 7 and Stripe security fixes
Developers pushed back hard on two WordPress 7.2 features, Stripe for WooCommerce fixed bugs that could allow fraudulent orders and Contact Form 7 bug details went public.
After two weeks of attacks on WordPress itself, this one was calmer. Nothing on my list is being attacked yet. Most of the noise came from WordPress 7.2, where two new features ran into a lot of resistance from developers (and, in one case, from Matt Mullenweg himself) a few days before the release candidate on 17 November.
For shops, the one to act on is Stripe for WooCommerce, which fixed bugs that could let someone place fraudulent orders. And if you use Contact Form 7, check it's on 6.2.4 or later before 19 November, when a demonstration of how to attack the old versions is due to be published.
WordPress 7.2 runs into resistance
Developers want /random/ off by default
Last week I wrote about the new /random/ address in WordPress 7.2, which sends visitors to a random post. I wasn't the only one with doubts. The announcement drew a wave of pushback, mostly over the feature being switched on for every site rather than being something you opt into.1 Comments raised the extra load on big sites, since anyone (or any bot) can hit the address over and over, along with the effect on analytics and the case that this belongs in a plugin, not core.2
Core committer Aaron Jorbin, who announced the feature, has opened a ticket to look at making it faster on very large sites. As of Saturday it's still on by default.2 Hosts are being asked to test it before release, because sites need their rewrite rules refreshed after upgrading for /random/ to work.3
If you'd rather not wait, Jono Alderson has released a small plugin, No Random Posts, that switches the feature off.2 It does nothing until 7.2 arrives, so there's no rush to install it, but it's an easy option for shops and business sites.
The Secrets API might not make it
The other row is about the new Secrets API, which gives plugins a safer place to store things like payment and email API keys. Today most plugins keep those keys as plain text in the database, where they end up in every backup.45
Ryan McCue, who created the WordPress REST API, asked for it to be taken out of 7.2. His argument is that secrets should be kept away from the rest of a site's data wherever possible, not managed by WordPress itself.6 Matt Mullenweg agreed with him in the comments, saying it's not a good time for WordPress to make itself a target for sensitive data like that. The API's author, Eric Mann, pointed out that the keys are already in the database unencrypted, and that pulling the feature leaves them that way.5
For now it's switched off on any site without a new encryption key in wp-config.php, and core doesn't use it yet, so nothing changes for you unless a plugin starts relying on it.3 I'd expect a decision before RC1 on Tuesday.
Apache has a critical bug only your host can fix
Like the Brotli bug last month, this one lives on the server, not in WordPress. Apache, the web server software many hosts run in front of WordPress, has a critical bug in the part that handles HTTP/2 connections. On an affected server it could let someone run their own code without logging in. Apache fixed it in version 2.4.71 on 11 November.7
It only matters if your site runs on Apache with HTTP/2 switched on, which has to be turned on in the server settings. Wordfence says it hasn't seen any public demonstration of the bug being used to take over a server, and nobody had reported attacks when the details came out.8
Updating WordPress, plugins or a security plugin won't fix it. Check your host's announcements, and if you can't find anything, ask them whether your server uses HTTP/2 through Apache and whether the fix is installed.8 If your host only uses LiteSpeed or nginx, with no Apache behind it, this one isn't for you.
WordPress news
WordPress 7.2 beta 5 sends an email when someone creates an application password
Beta 5 came out on Tuesday. The most useful change for site owners is an email whenever someone creates an application password, which is a common trick for keeping access to a hacked site. It also fixes all the known problems with PHP 8.6, which comes out on 19 November.9 Your plugins and theme need to be ready for PHP 8.6 too, so I wouldn't switch to it for a while. The final release is still due on 8 December.
Reprint copies a whole site to a new host or your computer
WordPress.org has released Reprint, a free plugin and command-line tool that copies a site's files and database to another server or your computer. It copies a piece at a time, can pick up again if the connection drops and fixes the links if the address changes.10 It looks handy for moving host or making a test copy. It's still at version 0.11, so I'd try it on a test site first, as WordPress.org suggests.
Mētis becomes WordPress's flagship theme
Mētis, which started out as an early design for the next default theme, is now WordPress's "flagship" theme, at Matt Mullenweg's request. It comes with six starter designs (business, news, magazine, portfolio, writer and personal), fifty patterns and six style variations.11 Ipsum is still the default theme in 7.2.
For developers
Gutenberg 24.4 adds search and filters to Notes, shows which block styles are overriding your Global Styles and adds an experimental wp-env runtime that uses your local PHP and SQLite.12 The Secrets API dev note covers the functions and the beta migration steps.4
Around the community
Kinsta adds Patchstack protection to every site it hosts
Kinsta now protects every WordPress site it hosts with Patchstack's firewall rules, at no extra cost and with nothing to set up. Patchstack says it blocked more than 1.5 million attack attempts across 68,000 Kinsta sites in its first few weeks.13 It's a good addition, but it's no substitute for updating.
In brief
Wordfence 9.1.0 adds a security news widget on the dashboard, gets new firewall rules onto sites faster and now logs failed logins through application passwords and the REST API, followed by a small 9.1.1 update.14 Automattic has launched Spacefast, a new company for publishing sites and apps people have built with AI tools.15 And looking back at last month's PHP2Shell scare, The Repository found no confirmed WordPress hacks from it.16
WooCommerce
Stripe for WooCommerce fixes bugs that could allow fraudulent orders
WooCommerce's Stripe extension had a security release on Wednesday. Update to 11.2.0, or 11.1.2 if you need to stay on the 11.1 line. WooCommerce says the most serious bugs could allow fraudulent purchases, and it has seen no evidence of them being used.17 Both versions need WordPress 6.9 and WooCommerce 11.0 or later, so you may need to update those first.
The same post also covers an older bug in version 10.9.0. If a shopper created an account at checkout and paid with Apple Pay or Google Pay through the Express Checkout buttons on the classic checkout, their new password was saved as plain text in the order details, where admins and shop managers could see it. Versions from 11.1.0 clean those up automatically and email the site admin if they find any.17 If your shop ran 10.9.0 with that setup, WooCommerce suggests checking backups and order exports for copies and asking those customers to reset their passwords.
WooCommerce 11.3 adds more sale badge options
WooCommerce 11.3.0 came out on Wednesday. The On-Sale Badge block can now show the amount or percentage off, catalogue blocks get more styling options, product gallery swiping feels more natural on mobile and there's a new setting for your refunds and returns policy page.18 It includes a database update, so take a backup first. WooCommerce said last week that a separate 11.3.1 security release would follow, but it hadn't appeared by Saturday evening.19
Plugin security updates
Contact Form 7: the details are now public
Contact Form 7 fixed this bug in 6.2.4 on 29 October, but the details only went public this week. Anyone could get a file past the upload checks on a form with a file upload field and have it stay on the server. On some servers (a standard Apache setup on Debian or Ubuntu, which lists folder contents publicly) that file could be run as code. Elsewhere it could still put a web page or image on your site that does things it shouldn't.20 WPScan plans to publish its demonstration on 19 November, and attacks tend to follow those.
Version 6.2.4 is stricter about uploaded file names, so test any forms that accept uploads after updating.21 Version 6.2.5 came out on Tuesday and fixes two smaller leaks, where mail tags and default values could show private post data or user details, so go straight to that.22
The rest of the week
I haven't seen reports of attacks on any of these:23
| Plugin | Sites | What's wrong | Fixed in | Action |
|---|---|---|---|---|
| Contact Form 7 | 10M+ | On 6.2 to 6.2.3, anyone could upload files through a form, and on some servers run them | 6.2.4 | Update now |
| Limit Login Attempts Security | 1M+ | Someone who already knew a password could skip the two-factor step | 3.4.1 | Update |
| Forminator | 600,000+ | If a payment gateway was disconnected, anyone could sign up through a paid registration form without paying, and get whatever role the form gives | 1.58.4 | Update |
| NextGEN Gallery | 300,000+ | Users allowed to manage galleries could delete any file on the server | 4.5.6 | Update |
| Optimole | 200,000+ | Anyone could plant code that runs for visitors, or set up a file deletion triggered when an admin renames an image | 4.2.20 | Update |
| Widget Options | 100,000+ | Authors could slip in code that runs on every page | 4.2.7 | Update |
| Everest Forms | 90,000+ | With its Save and Continue add-on and one setting, anyone could delete uploaded files | 3.6.4 | Update |
| Ultra Addons for Contact Form 7 | 60,000+ | Anyone could read files on the server | 3.5.55 | Update now |
| Ninja Forms File Uploads | Premium | Anyone could delete any file on the server, including the one that holds your database password | 3.3.37 | Update now |
The latest versions of Limit Login Attempts Security (3.4.3) and Ultra Addons for Contact Form 7 (3.5.57) include further security fixes, so update to those. Forminator and Ninja Forms File Uploads fixed their bugs around the turn of the month, and Ultra Addons in early October, so plenty of sites will already be up to date.23
Bugs in other popular plugins need an account or an unusual setup, but they're worth updating: Redux Framework 4.5.18, JetFormBuilder 3.6.8.1, Strong Testimonials 3.3.18, iubenda 3.13.7 and Defender Security 6.4.1 (two-factor codes weren't rate limited by default). The forum plugin wpForo (20,000 sites) fixed bugs that let anyone pull data out of the database, so update it to 3.2.5. WPML 5.0, from September, fixed a narrow bug that could let someone take over an account while its owner was logging out, on sites that use a separate domain for each language.2324 If you're not sure how to handle any of this, see my guide to dealing with a plugin security vulnerability.
For the long tail, Wordfence's report for 2 to 8 November counted 497 new vulnerabilities across 312 plugins and one theme, 40 of them still unpatched.25
What I'd do this week
- Check Contact Form 7 is on 6.2.5 (or at least 6.2.4) before 19 November, then send a test through any form that takes file uploads. If it stops sending, here's how to fix a contact form that won't send email.
- Update Stripe for WooCommerce to 11.2.0 (or 11.1.2). Check you're on WordPress 6.9 and WooCommerce 11.0 or later first, and take a backup. If anything goes wrong, see how to fix a site after a bad update.
- Ask your host about the Apache HTTP/2 fix if your site runs on Apache and you can't find an announcement.
- Update Forminator, Optimole, Limit Login Attempts Security and Ninja Forms File Uploads if you use them, then anything else from the table.
- Hold off on PHP 8.6 when it comes out on 19 November, until your plugins and theme say they support it.
- Decide what to do about /random/ before 7.2 arrives on 8 December. For a shop or business site, I'd plan to switch it off.
Developers Push Back on WordPress 7.2's New /random/ Endpoint Being On by Default, The Repository, 9 November 2026. ↩
Your Content Is Going To Get More Random! (comments), Make WordPress Core, comments from 9 to 13 November 2026. ↩ ↩ ↩
Call to test: WordPress 7.2's Secrets API, upgrades and /random/ on your hosting platform by November 17, Make WordPress Hosting, 12 November 2026. ↩ ↩
The Secrets API in WordPress 7.2, Make WordPress Core, 11 November 2026. ↩ ↩
The Secrets API in WordPress 7.2 (comments), Make WordPress Core, comments from 12 and 13 November 2026. ↩ ↩
WordPress 7.2's Secrets API Faces Pushback as Hosts Are Asked to Test It Before RC1, The Repository, 13 November 2026. ↩
Apache HTTP Server 2.4 vulnerabilities, Apache Software Foundation, 11 November 2026. ↩
PSA: Critical Apache HTTP/2 Vulnerability: What WordPress Site Owners Should Know, Wordfence, 12 November 2026. ↩ ↩
WordPress 7.2 Beta 5, WordPress.org, 10 November 2026. ↩
Copy Your WordPress Site with Reprint, WordPress.org, 13 November 2026. ↩
Introducing Mētis, Our New Flagship Theme, Make WordPress Core, 13 November 2026. ↩
What's new in Gutenberg 24.4? (12 November), Make WordPress Core, 13 November 2026. ↩
Kinsta now protects every WordPress site it hosts with Patchstack, Patchstack, 12 November 2026. ↩
What's New in Wordfence 9.1.0: Security News, Faster Rules and Smarter Alerts, Wordfence, 10 November 2026. ↩
Automattic Launches Spacefast, a Platform for AI-Built Sites and Apps on WordPress.com's Infrastructure, The Repository, 13 November 2026. ↩
No Confirmed WordPress Hacks, but PHP2Shell Shows How Hosting Companies Handled a Security Crisis, The Repository, 11 November 2026. ↩
Security fix for WooCommerce Stripe Gateway: update to 11.2.0 or 11.1.2, WooCommerce Developer Blog, 11 November 2026. ↩ ↩
WooCommerce 11.3.0: Release notes, WooCommerce Developer Blog, 11 November 2026. ↩
We went looking: what Woo has done about security since June, WooCommerce Developer Blog, 6 November 2026. ↩
Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload via Invalid UTF-8 Filename, WPScan, 5 November 2026. ↩
Contact Form 7 6.2.4, Contact Form 7, 29 October 2026. ↩
Contact Form 7 6.2.5, Contact Form 7, 10 November 2026. ↩
National Vulnerability Database, NIST, with records from Wordfence and WPScan published 7 to 14 November 2026. Fixed versions checked against each plugin's changelog on WordPress.org or the vendor's site. ↩ ↩ ↩
WPML Multilingual CMS 5.0, WPML, 13 September 2026. ↩
Wordfence Intelligence Weekly WordPress Vulnerability Report, 2 to 8 November 2026, Wordfence, 12 November 2026. ↩