Skip to main content

Your privacy

We store what the site needs to work, like a notice you closed or your domain shortlist. With your OK we also use Google Analytics to see which pages help people, and the Meta Pixel to measure which of our adverts work. Privacy policy

Serverlys

WordPressServerlys team7 min read

WordPress 7.1.5 fixes 20 security issues: update now, then get ready for 7.2

Summarize with:

Share:

WordPress 7.1.5 patches 20 security issues, including an unauthenticated flaw that could lead to remote code execution. What it fixes, how to check you have it, and what changes when 7.2 arrives on December 8.

On November 18, 2026, WordPress released version 7.1.5, a security release with 20 security fixes. The official announcement asks site owners to update immediately, and this time that advice matters more than usual. One of the issues can be reached by a visitor who is not logged in, and WordPress says it "could lead to remote code execution", which means someone running their own code on your server.

It lands one day after the first release candidate of WordPress 7.2, which is due on December 8. This guide covers what 7.1.5 fixes, how to make sure your site actually has it, and what to check before 7.2 arrives.

What WordPress 7.1.5 fixes

The release notes list 20 items. Eighteen are vulnerabilities and two are hardening changes. Sorting them by who can trigger them shows what is urgent, because a flaw any visitor can reach is far more dangerous than one that needs an administrator's password.

Anyone on the internet (no login needed)

  • Privilege escalation through Template Part block attributes, which WordPress says could lead to remote code execution. This is the headline fix.
  • Stored cross-site scripting (XSS) through shortcode attributes in comments. Any site with open comments is exposed.
  • Denial of service through batched XML-RPC pingbacks, which could be used to overload a server.
  • Disclosure of private taxonomy terms through the REST API search.

Logged-in users with low-level roles

  • Subscriber and above: information disclosure through XML-RPC wp.getComments.
  • Contributor and above: three stored XSS issues, through oEmbed provider responses, the Comment Date block's date format, and media filenames when a media block is converted to a File block.
  • Author and above: disclosure of users' email addresses through the REST comments endpoint, and an authorization bypass when editing comments in the admin.
  • Editor and above: information disclosure through post and template author assignment in the REST API.

Administrators and other issues

  • Stored XSS through Customizer previews, and on Multisite networks, a way for a site Administrator to take over a Super Admin account through Customizer menu previews.
  • Two SQL injection issues, one in WP_Meta_Query through nested relation values and one through the front page setting in Customizer changeset previews.
  • Three further XSS issues: in the legacy media library popup, in wp_interactivity_data_wp_context(), and in the block editor through Openverse image metadata.
  • Two hardening changes: a stricter match for JSON media types and removal of the Imgur embed variation.

WordPress has not said that any of these is being exploited, and the full technical details are not public yet. That is normal for a coordinated security release, and it is exactly why the window right after release is the one to act in: once a fix is public, attackers can study it to work out what it was fixing.

Running an older version of WordPress?

WordPress says the fixes are being backported to every branch that still receives security updates, currently back to 4.7, and that those backports ship as they become ready. So a site on an older major version can still get patched without a major upgrade.

Treat that as a safety net, not a plan. Only the latest version is actively supported. If a site is stuck on an old version because a plugin or theme breaks on newer ones, that plugin or theme is the real risk. Replace it, or have the site moved to a current, supported setup.

How to check your site is updated

WordPress says sites that support automatic background updates will start updating on their own. That covers most sites. It does not cover all of them, because hosts, security plugins and a single line in wp-config.php can turn automatic updates off. Check rather than assume:

  1. Take a backup if your site has not been backed up in the last day. Our backup tutorial covers the options.
  2. Open Dashboard → Updates. The top of the page shows your version. Anything older than 7.1.5 on the 7.1 branch needs updating, so click Update Now.
  3. Look in wp-config.php for AUTOMATIC_UPDATER_DISABLED set to true or WP_AUTO_UPDATE_CORE set to false. Either one stops security releases installing on their own.
  4. If you manage several sites, wp core version in WP-CLI tells you the version in seconds and wp core update applies the update.
  5. Update plugins and themes too, and delete any you no longer use. Most WordPress break-ins start with an out-of-date plugin, not with WordPress itself.
# Check and update WordPress core with WP-CLI
wp core version
wp core update
wp core verify-checksums

wp core verify-checksums compares your core files with the official copies, which is a quick way to spot files someone has tampered with. If it reports changes you did not make, or the site behaves strangely after the update, follow our hacked website recovery guide.

WordPress 7.2 arrives on December 8

The first release candidate of WordPress 7.2 came out on November 17, and the RC1 announcement puts the final release on December 8, 2026. A release candidate means the features are frozen, so what is in RC1 is what will ship. The highlights:

  • Ipsum, a new default theme.
  • More Gallery block controls, plus new Global Styles and typography tools.
  • Canvas Notes and a DataForm-based settings inspector for blocks in the editor.
  • Faster media uploads and redrawn SVG admin icons.
  • An "On This Day" dashboard widget and random post discovery.
  • Accessibility, security and PHP 8.6 compatibility improvements.

Changes from what was announced earlier

If you read our earlier WordPress 7.2 preview, two plans have changed since:

ItemEarlier planNow
Secrets APITentatively in 7.2, through WP-CLI onlyNo longer shipping with 7.2, per the developer note updated November 17
jQuery 4Preparation under wayNot in 7.2. It ships jQuery Migrate 3.6.0 to prepare, and jQuery 4 itself is tentatively planned for 7.3

What your developer should check

According to the REST API developer note, 7.2 makes three REST API changes, and two of them change data that existing code may rely on:

  • Revision and autosave responses only include revisioned meta. Code that reads other meta from those responses will get less than before.
  • The comments endpoint `status` parameter is now an array. Code that compares it to a single string needs updating.
  • A new `rest_allowed_cors_methods` filter. The default behaviour does not change.

These mostly affect custom plugins, headless sites and apps that talk to WordPress through its API. A typical brochure site or WooCommerce store using well-maintained plugins will not notice them, but it is worth asking whoever built your site.

How to test 7.2 without risking your live site

  1. Make a staging copy of your site. Our guide to setting up a WordPress staging site walks through it.
  2. Install the WordPress Beta Tester plugin on the copy and switch it to the release candidate channel.
  3. Click through every page that earns you money: home page, service and product pages, contact form, booking, basket and checkout.
  4. Open the editor and edit a page using the blocks you actually use, especially Gallery.
  5. Report anything that breaks to the plugin or theme author now, while there is still time before December 8.
Security releases cannot wait for a quiet week. Major releases can wait until you have tested them.

Frequently asked questions

Is WordPress 7.1.5 safe to install right away?

Yes. It is a security release on the current 7.1 branch, not a new major version, so it fixes problems without adding features. WordPress recommends installing it immediately. Take a backup first as a matter of habit.

Will my site update to 7.1.5 automatically?

If automatic background updates are enabled, which is the default, yes. Your host, a security plugin or a setting in wp-config.php may have turned them off, so confirm the version on Dashboard → Updates instead of assuming.

Should I install WordPress 7.2 on December 8?

Install it once your staging copy passes. Many owners wait a few days for the first 7.2.x maintenance release. That is reasonable for a major version, but never a reason to skip security releases on the version you are running.

Was my site hacked through one of these flaws?

WordPress has not reported attacks using them. Warning signs of a compromise include unknown admin users, unfamiliar plugins, spam pages showing in Google, or redirects you did not set up. If you see any of these, read our guide to what to do when your website is hacked.

Where Serverlys can help

If you would rather not watch WordPress release notes at all, this is what our WordPress plans are for:

If you need…Start withFrom
Hosting with free SSL and daily backups, so an update is never a riskWordPress hosting$7.95/mo, renews at $7.95/mo
Someone to apply WordPress, plugin and theme updates for you every month, with daily backups and uptime alertsServerCare Essential$149.95/mo
A site stuck on an old WordPress version moved to a current, supported setupFree migrationFree with hosting

The author

Serverlys team

The people who run Serverlys hosting, domains and support. We write about what we see every day helping small businesses keep their websites fast, safe and online.

More from Serverlys team

A plan that still makes sense in year two

Free migration, free SSL and daily backups on every plan, with a 30-day money-back guarantee.

Prefer the phone? (305) 671-1272 · Existing customer? Client login