WordPress 7.1.5 Security Release: What Changed and Why

WordPress 7.1.5 security release card

WordPress 7.1.5 came out on 18 November 2026, three weeks after 7.1.4. It’s a security-only release, and the official announcement says “it is recommended that you update your sites immediately.” The headline bug is described as an unauthenticated privilege escalation that “could lead to remote code execution”. Here’s what that really means for your site.

Last updated 21 November 2026. We read the WordPress.org release post and the 7.1.5 documentation page, plus write-ups from Patchstack, Pantheon and Search Engine Journal. We also downloaded the official 7.1.4 and 7.1.5 zip files and compared them file by file. We didn’t try to exploit anything, we didn’t test the backported releases for older branches, and we haven’t seen the researchers’ own reports, which aren’t public.

The short version

  • Update to 7.1.5, or to the latest release of your branch if you’re on an older one.
  • If minor auto-updates are on (the default), you probably already have it. Check anyway, it takes ten seconds.
  • The biggest risks are on multisite networks and on sites where other people can log in or leave comments.
  • No CVE numbers had been assigned when Patchstack published, and when we checked on 21 November, CISA’s list of actively exploited bugs had no entry for anything fixed in 7.1.5.

18 fixes or 20?

You’ll see both numbers, and both are right. The release post lists 20 items. Two of them are labelled as hardening rather than vulnerabilities: a too-loose pattern for spotting JSON content, and the removal of the block editor’s Imgur embed, whose provider no longer exists. Search Engine Journal counts “18 vulnerabilities plus two security improvements”. Pantheon says it “fixes 20 issues”. WordPress’ own documentation page counts all 20 when it says which old branches are affected.

The fixes that matter most, in plain words

The “who can trigger it” column comes from Patchstack’s breakdown, which is the clearest one we found.

Fix Who can trigger it What it means
Template Part block privilege escalation, possible RCE No account needed, but a logged-in editor has to open the attacker’s content The block editor could be tricked into sending requests to the wrong part of your site, using the editor’s own login
Multisite: site Administrator to Super Admin An Administrator of one site on a network One site’s admin could take over the whole network
SQL injection in WP_Meta_Query No account needed, but only if a plugin or theme passes visitor input into a meta query Database commands smuggled in through a search or filter
Stored XSS via shortcode attributes in comments No account needed, plus a page with a Latest Comments block A comment could run code in the browser of anyone viewing that page
XML-RPC pingback denial of service No account needed One request could make the site process an unlimited number of pingbacks
Private taxonomy terms via REST search No account needed Visitors could see category-style terms that were meant to be hidden
Four stored XSS bugs Contributor or higher, or an Administrator for the Customizer one Matters on sites with several writers

The rest are smaller leaks and permission slips, like Subscribers reading commenter emails and IP addresses through XML-RPC. Anthropic is credited with reporting two of the 20.

About “unauthenticated” on the headline bug

It doesn’t mean a stranger can type a URL and own your site. Patchstack lists the requirement as “Nothing (Unauthenticated), and an editor user opens the content”. The attacker needs no account, but someone who can use the block editor has to open the poisoned block. Patchstack also explains the path to code execution: from the tricked editor, an attacker could reach an administrator’s own plugin-install endpoints, “with the administrator’s own credentials.” So the danger is real, but it needs a logged-in person to take part. Compare that with wp2shell in July, which needed no login and no click at all.

Neither WordPress nor Patchstack says how an attacker would get the block in front of an editor, and we won’t guess. Update anyway.

What the code actually changed

We compared the official 7.1.4 and 7.1.5 downloads. 27 files changed and one was added. The added file is a small developer config file in the Twenty Twenty-Five theme folder, with no effect on your site. Of the 27, 19 are PHP files carrying fixes, two are the version number and the About screen, and six are JavaScript: three editor packages, each in a normal and a minified copy.

What the diff shows:

  • Template Part (JavaScript, core-data.js). A new check called isSafeEntityKey() now looks at the ID the editor uses to load or save something. It rejects IDs containing an encoded slash, a ?, #, &, a backslash or control characters, and IDs with . or .. path pieces. Before, a crafted ID could point the editor’s request at a different address. The check runs when the editor reads, saves or deletes a record, checks permissions, and loads revisions and autosaves. A bad ID now just throws “Invalid entity record key.”
  • Meta query SQL injection (class-wp-meta-query.php). A new sanitize_relation() function forces the “relation” value to be exactly AND or OR, including inside nested queries. Anything else becomes AND.
  • Customizer front-page SQL injection. formatting.php now treats any show_on_front value other than page as posts. Previewed Customizer values now go through the same cleaning as saved ones. class-wp-query.php also swaps about a dozen spots where values were pasted straight into SQL for $wpdb->prepare(), the safe way.
  • Multisite takeover (class-wp-customize-nav-menus.php). A one-line change: the security hash for menu previews now starts with customize_nav_menu_args|, so it can’t be swapped with a hash WordPress makes elsewhere.
  • Comment shortcodes (shortcodes.php). Escape codes like \x3c in shortcode attributes used to turn back into <. Now they become harmless text.

If you track changed files, note that Patchstack says five of the fixes live in the editor’s JavaScript, not in PHP.

Who is actually at risk

  • Multisite networks. If you hand out site Administrator roles to clients or students, the Super Admin bug is the one to care about. Patchstack’s advice is to review your Administrator list.
  • Sites with several writers or open comments. Three of the XSS fixes need only a Contributor account, and two of the no-login bugs come in through comments or blocks someone else creates.
  • Sites with XML-RPC open. The pingback bug needs no login. It can slow a site, not take it over.
  • A single-admin blog with comments off has much less exposure. It still needs the update.

What to do today

  1. Check your version. Go to Dashboard > Updates. Or, with WP-CLI, run wp core version. It should say 7.1.5, or the latest release for your branch (table below).
  2. Check that auto-updates for minor releases are on. They are by default: in WordPress’ updater code, the minor setting starts as enabled. The Updates screen should say “This site is automatically kept up to date with maintenance and security releases of WordPress only” or “with each new version of WordPress”. If it says “This site will not receive automatic updates”, someone turned them off, usually with WP_AUTO_UPDATE_CORE set to false or AUTOMATIC_UPDATER_DISABLED in wp-config.php.
  3. Freelancers, watch for Git. If the Updates screen says “This site appears to be under version control”, WordPress won’t auto-update. Those sites need a manual update or a deploy.
  4. Ask your host if it pins versions. Managed hosts sometimes hold core updates back to test them. Pantheon, for example, ships 7.1.5 as an upstream update you apply yourself. It also deployed firewall rules early for some of these bugs, and says plainly that they “do not replace the update.”
  5. Update by hand if needed. Click “Update Now”, or run wp core update --minor to stay on your branch.

On an older branch?

WordPress backported the fixes all the way to 4.7. Older branches are affected by fewer of the 20, because some of the buggy code didn’t exist yet. From the 7.1.5 documentation page:

Branch Patched release Affected by
7.0 7.0.9 all 20
6.9 6.9.12 all 20
6.8 6.8.13 all 20
6.4 6.4.15 19 of 20
5.9 5.9.21 17 of 20
5.4 5.4.26 13 of 20
4.7 4.7.40 11 of 20
4.6 and older none no longer get security updates

Two catches. WordPress calls these backports “a courtesy” and says “only the most recent version of WordPress is actively supported.” On 4.6 or older, nothing is coming: plan a move to a current version, tested on a copy of the site first.

Where 7.1.5 fits

This is the latest in a long run. We count every security release since July, 7.1.5 included, in our post on why WordPress keeps shipping security updates: eight releases and 64 fixes. Just before this one, 7.1.4 arrived on 28 October with fixes including a race condition in the update process itself (CVE-2026-119977). CISA added that bug to its Known Exploited Vulnerabilities catalog on 3 November, meaning there was evidence of real attacks. We covered it in our post on the core upgrader flaw.

Nothing in 7.1.5 is in that catalog yet. But the 7.1.4 bug shows how short the gap between “fix published” and “attacks start” has become. Once a fix is out, anyone can compare the files, the way we just did.

Can a firewall cover you until you update?

Partly. Pantheon’s early firewall rules are an example of virtual patching: blocking the attack pattern at the edge before the real fix is installed. We explained how it works, and where it falls short, in virtual patching explained. Bugs that run inside a logged-in editor’s browser, like the Template Part one, are hard for a firewall to spot. Treat a firewall as a stopgap and update.

Frequently asked questions

Did my site update to WordPress 7.1.5 automatically?

Probably, if minor auto-updates are on, which is the default. Check the Updates screen in your dashboard or run wp core version. Sites under Git, sites with WP_AUTO_UPDATE_CORE set to false, and some managed hosts that ship core updates on their own schedule won’t update by themselves.

Can someone hack my site with the 7.1.5 bugs without logging in?

Some bugs need no account, but most still need a step from someone on your site. The headline Template Part bug needs a logged-in editor to open the attacker’s content, and the comment XSS needs a page with a Latest Comments block. The XML-RPC bug can slow a site down without any login.

I’m on WordPress 6.4. Do I have to upgrade to 7.1?

Not for these fixes. WordPress released 6.4.15 with the fixes that apply to 6.4, and every branch back to 4.7 got a patched release. Only 7.1 is actively supported, though, so plan a move to the current version.