twimco.Let’s talk ↗︎
Menu
Field notes / Commerce

WordPress 7.1.5 fixes 20 security bugs a week before Black Friday. Update tonight, even in a code freeze

Your store is in code freeze, Black Friday is a week away, and WordPress just shipped twenty security fixes. Here's how to tell whether the update already landed, and the order to do it in tonight if it didn't.

Editorial illustration of a shop owner and a developer working late in the back room of a small online store stacked with shipping boxes, she at a laptop under a desk lamp and he checking a test order on his phone, with a checklist, a backup drive and a calendar with one day circled beside them.

Update now, freeze or not. WordPress 7.1.5, released November 18, 2026, fixes 20 security issues, four reachable without logging in, including one WordPress says could lead to remote code execution. No attacks had been reported by this evening. Many sites updated themselves, so check the version first. If yours didn't, back up, update core on its own (staging first only if it matches live), then place a test order.

The one update your freeze should let through

If you run a WordPress shop, someone on your team probably said it last week: nothing ships until after Cyber Monday. It's a good rule. Tonight it needs an exception.

WordPress 7.1.5 came out this afternoon, November 18, a little after noon Eastern. It's a security release with twenty fixes and no new features, and WordPress's own advice is to update your sites immediately. Four of the fixes can be reached by someone who has never logged in to your site: a stored cross-site scripting bug that rides in on shortcodes in comments, a leak of private taxonomy terms through the REST API, a denial of service through batched XML-RPC pingbacks, and a privilege escalation through Template Part block attributes that WordPress says could lead to remote code execution. There are also two SQL injections and a multisite bug that lets a site Administrator take over a Super Admin account.

As of this evening, nobody has reported attacks on any of these, and no CVE numbers had been assigned when Patchstack published its analysis. That's the good news. The less good news is how the last release went. WordPress 7.1.4 shipped on October 28. According to Wordfence, the first request probing its headline bug arrived nine minutes after Wordfence's firewall rule went live, and Wordfence has since reported blocking more than 240,000 attempts. CISA added that bug to its list of actively exploited vulnerabilities on November 3. heise made the same point tonight: after a WordPress security release in late September, attacks started within hours.

A code freeze protects the store from your changes. It was never meant to protect it from security fixes. A point release like this replaces core files nobody on your team edits, and its whole job is to keep the store working the way it does today.

First, check whether it already happened

Most WordPress sites install security releases on their own. WordPress says sites that support automatic background updates will start the update by themselves, and this evening WordPress.org's update service was already offering 7.1.5 as an automatic update. Managed hosts handle it too. Fasthosts, for one, told customers on its managed WordPress plan that it's updating them automatically and no action is needed, while customers on its regular web hosting, VPS and server plans have to update themselves.

So before you touch anything, look:

  • The Dashboard. Dashboard > Updates shows the version you're on. You want 7.1.5, or the fixed release for an older branch: 7.0.9, 6.9.12, 6.8.13 and so on, all the way back to 4.7.40. The full list is on the WordPress 7.1.5 HelpHub page. Anything on 4.6 or older gets no fix at all.
  • The admin inbox. When a background update works, WordPress emails the site's admin address with a subject like "Your site has updated to WordPress 7.1.5". Search for it. If that address is a former employee's mailbox, put fixing it on this week's list.
  • The command line, if you have one. wp core version prints the version. wp core verify-checksums compares your core files with WordPress.org's copies and flags anything that doesn't match.

Here's the part that catches carefully built stores. Automatic updates quietly skip a few common setups: a site deployed from Git or Composer (WordPress holds off on background updates when it sees version control), a wp-config.php with AUTOMATIC_UPDATER_DISABLED, WP_AUTO_UPDATE_CORE set to false or DISALLOW_FILE_MODS turned on, or a host that switched updates off. Those tend to be the stores with a developer, a deploy process and a strict freeze. If yours is one of them, nobody has updated it but you.

A code freeze protects the store from your changes. It was never meant to protect it from security fixes.

Staging first, or straight to live?

This is the decision that actually eats the evening, so here's how we'd make it.

Go through staging first if you have a staging copy that really matches live (same plugins, same theme, same PHP version, reasonably fresh data) and someone can test it tonight. Update staging, then spend fifteen minutes on the paths that make money: a product page, add to cart, checkout with a test payment, the order confirmation email, and the order screen in the admin. If those pass, do live. We've written about when a staging site can be trusted. The short version: a copy nobody has refreshed since summer isn't telling you much.

Go straight to live if your staging doesn't match, or doesn't exist, and you can take a fresh backup you know how to restore. A small security release tested on a stale copy proves less than a careful live update with a working backup. And building proper staging first leaves the store unpatched for days, in the week you can least afford it.

Either way, update WordPress on its own. This isn't the night to clear the plugin update queue too. WooCommerce 11.3.0, the current version, lists itself on WordPress.org as tested up to WordPress 7.1.5, so the core update shouldn't need a WooCommerce change. If you haven't installed 11.3 yet, that's a separate update with its own database step, and our WooCommerce 11.3 note covers doing it with a rollback plan. One change at a time means that if something breaks, you know which change did it.

Decision guide

Staging first, or straight to live?

ConsiderationStaging first whenStraight to live when
Your staging copyMatches live: same plugins, theme and PHP, refreshed recently.Is missing, or months out of date.
Who can testSomeone can run checkout on staging tonight.It's just you, with a backup you've restored before.
How you deployGit or Composer deploys already pass through staging.One site, updated from the Dashboard.
What you testProduct page, cart, checkout and order email on staging, then one order on live.One small real or test-mode order on live right after the update.
Decision framework: assess these conditions against your own store. Illustrative, not client data.

Tonight, in this order

  1. Confirm the version. If it already says 7.1.5, or your branch's fixed release, skip to step 6.
  2. Pick your quietest hour. Look at orders by hour and choose the lowest. Tell whoever watches orders and support what you're doing and when.
  3. Back up the database and the files, and know where the restore button is. A host snapshot counts if you've seen one restored before.
  4. Still on 7.1.3 or older? Close the upgrade folder first. The previous release, 7.1.4, fixed the bug attackers went after in October: for a few seconds while an update unpacks, a copy of WordPress sits in wp-content/upgrade/, and on many servers the web can reach it. Rescana points out that if your site skipped 7.1.4, tonight's update is still unpacked by the old code. Patchstack's advice is to deny web access to wp-content/upgrade/ at the web server. WordPress only needs that folder on disk, not on the web, and your host or developer can add the rule in a few minutes.
  5. Update. Dashboard > Updates > Update Now, or wp core update from the command line. On a Git or Composer site, the new version goes out through your normal deploy. That's fine, as long as the deploy happens tonight.
  6. Check it. The version reads 7.1.5. The checksums pass. Place one small real order, or a test order through your payment provider's test mode, and refund it. Make sure the confirmation email arrived.
  7. Write it down. One line in the freeze log: what changed, when, and who checked it. When someone asks on Black Friday morning whether anything changed this week, the answer is already there.

Sequence of work

Tonight's order of operations

  1. Check the version

    7.1.5 or your branch's fix? You may already be done.

  2. Back up

    Database and files, with a restore you know works.

  3. Close the upgrade folder

    On 7.1.3 or older, deny web access to wp-content/upgrade/ first.

  4. Update core on its own

    No plugin updates in the same window.

  5. Check and log it

    Version, checksums, one test order, one line in the freeze log.

Illustrative sequence based on WordPress's and Patchstack's guidance for the 7.1.4 and 7.1.5 releases; not a client screenshot.

Two fixes worth a second look

Most of the twenty need nothing from you beyond the update. Two are worth understanding because of how they'd reach a shop.

The Template Part bug. According to Patchstack's analysis, an attacker gets crafted block markup in front of someone who can edit the site. When that person opens it in the editor, the editor sends requests to endpoints the attacker chose, using that person's login. From an administrator's login, that reaches the plugin installer, which is the route to running code on your server. It counts as unauthenticated because the attacker never needs an account of their own. Until you're updated, think twice before opening content in the editor that you didn't write and don't recognise.

The comment bug. The stored cross-site scripting through shortcode attributes in comments needs one more piece to fire, Patchstack says: a page that shows comments through the core Latest Comments block. If any page on your site uses that block, it's one more reason to do this tonight rather than Monday.

While you're in the admin, take Patchstack's other suggestion and look at who has Contributor access or higher. Six of the fixes are about what those roles can reach, and that list tends to collect holiday temps, a past agency and the freelancer from two years ago. If you run multisite, check the Administrator list too.

If you'd rather someone else did this tonight

None of this is hard. It's just easy to push back when the week is full of promotions, inventory counts and ad budgets. The risk lives in the gap between "WordPress fixed it" and "our store is running the fix", and only you can close that one.

If your shop runs on WordPress and WooCommerce, it's deployed in a way that skips automatic updates, or nobody is quite sure who updates it, that's work our ecommerce team does: keeping a store current without breaking checkout, especially in the weeks that count. Tell us what you're running and we'll help you get it patched, checked and written down before Black Friday.

Related work: Paddle8.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎