Security

WordPress 7.1.5: 20 Security Fixes, a No-Login Path to Code Execution, and Backports to 4.7

A soft documentary photograph inside an old wooden greenhouse with rows of seedlings on benches, where several cracked glass panes along one wall have just been replaced with new clear panes and the old cracked panes lean against the wall below, a visual for WordPress 7.1.5, the security release that replaces many weak spots at once

WordPress 7.1.5 shipped on November 18, 2026, as a security release with 20 fixes. The most serious is a privilege escalation through Template Part block attributes that needs no login and, according to WordPress, could lead to remote code execution.

This post follows our WordPress 7.1.4 post from three weeks ago. It covers what WordPress 7.1.5 fixes, which issues need no account, which older branches got the same fixes, and what to check on client sites. Facts are as of November 20, 2026.

The short version: update every site to WordPress 7.1.5, or to the latest release on its branch, and confirm the update ran. Five of the fixes need no account, by WordPress’s and Patchstack’s counts. If your sites run multisite, or give Contributor, Author or Editor accounts to many people, review those accounts this week. Managed hosts may have added firewall rules, but those do not replace the update.

What WordPress 7.1.5 fixes

The WordPress 7.1.5 release post, written by Jeremy Felt, calls it a security release and recommends that you update your sites immediately. Jeremy Felt, Jerry Jones and Jarda Snajdr led the release.

The release post and the WordPress 7.1.5 version page on HelpHub list 20 entries. Eighteen are vulnerabilities. Two are hardening changes: a fix to a loose pattern that matched JSON media types too broadly, and the removal of the block editor’s Imgur embed variation, whose provider no longer exists.

Two of the fixes are credited to Anthropic, as were two in 7.1.4. Our 7.1.4 post explains WordPress’s use of Anthropic’s free scanner for open source projects. Neither WordPress page lists CVE IDs.

The WordPress 7.1.5 fixes at a glance

This table groups the 18 vulnerabilities by the access level the release post gives. Where it gives none, the table says so.

Fix Account needed Credited to
Privilege escalation through Template Part block attributes, could lead to code execution None Logan Homolka
Stored XSS through shortcode attributes in comments None Rafie Muhammad
Denial of service through batched XML-RPC pingbacks None Giovanni Cintolo
Private taxonomy terms exposed through REST API search None Anthropic
SQL injection in WP_Meta_Query through nested relation values Not stated (none, per Patchstack) Christiaan Swiers
Reflected XSS in the legacy media library popup Not stated Anthropic
XSS in the Interactivity API context function, and XSS through Openverse image data Not stated Juliette Reinders Folmer; Shu Takahashi
Site Administrator can take over a Super Admin account (multisite) Administrator Yuval Miller
Stored XSS and SQL injection through Customizer previews Administrator (per Patchstack for the SQL injection) Weston Ruter; Rudy Faile
Stored XSS in the Comment Date block, through oEmbed responses, and through media filenames Contributor or higher Several researchers
Comment editing authorization bypass; user emails exposed through REST comments Author or higher Jesse McNeil; Ben Bidner
Post and template author assignment exposed through REST Editor or higher Jarda Snajdr
Comment data exposed through XML-RPC wp.getComments Subscriber or higher Jaewook Lee

Five WordPress 7.1.5 fixes need no account

WordPress marks four fixes as unauthenticated. Patchstack says a fifth, an SQL injection, is open to anonymous callers too.

Template Part block attributes. The release post rates this an unauthenticated privilege escalation that could lead to remote code execution. Patchstack published an analysis of WordPress 7.1.5 on release day. Patchstack is a security vendor, so treat its write-up as its own research. According to Patchstack, crafted block markup can make the editor send requests to endpoints the attacker picks, using the logged-in user’s session. The attacker needs someone who can open that content to open it. Patchstack says the step to code execution goes through the administrator’s plugin install endpoints.

SQL injection in WP_Meta_Query. The release post does not state an access level. Patchstack says it is open to anonymous callers when site code passes request data into a meta query. That puts the risk on custom themes and plugins that build queries from URL parameters, such as filters on directory or event listings.

Stored XSS through comment shortcodes. Anyone who can post a comment can plant it. Patchstack says the site must show a page with the core Latest Comments block.

XML-RPC pingbacks. Batched pingback requests could slow or stop a site. Many sites never use XML-RPC.

Private taxonomy terms. The REST API search endpoint could show terms that should stay private. For most sites this is a small leak, but some use private terms for internal labels.

Logged-in roles still matter

Most of the rest need an account. That sounds limiting, but many of our readers run sites with exactly these roles. Association blogs take posts from member authors. Universities give Contributor accounts to student workers. Nonprofits bring in freelance writers.

Patchstack points to the Comment Date block bug as the one XSS in this release that needs no click. A Contributor’s markup runs for every visitor who loads the page.

The multisite fix also stands out. On a network, a site Administrator could take over a Super Admin account through Customizer menu previews. Universities and large associations often run multisite with many site admins. Patchstack advises reviewing those admin lists.

Which WordPress versions are fixed

WordPress only actively supports the newest version, but it backports security fixes. HelpHub lists a fixed release for every branch back to 4.7. Here is a sample.

Branch Fixed release Issues that apply
7.1 7.1.5 All 20
7.0 7.0.9 All 20
6.9 6.9.12 All 20
6.8 6.8.13 All 20
6.5 to 6.7 6.5.15, 6.6.12, 6.7.12 All 20
6.0 to 6.4 6.0.19 to 6.4.15 18 or 19 of 20
5.0 to 5.9 5.0.32 to 5.9.21 12 to 17 of 20
4.7 4.7.40 11 of 20

The release post said older-branch backports were in progress and would ship as they were ready. The WordPress releases page lists fixed releases dated November 18 for every branch we checked, 7.0 through 6.1. WordPress 4.6 and earlier get no security fixes.

WordPress 7.2 is still planned for December 8. The release post says WordPress 7.2 RC2 also shipped with the fixes that apply. If you are testing 7.2 with our WordPress 7.2 RC1 guide, move test sites to RC2.

A note on the WordPress 7.1.5 file list

HelpHub’s file list for WordPress 7.1.5 says no packages were revised. Patchstack says that list is incomplete. By its count, five of the 20 fixes come from an update to bundled block editor (Gutenberg) packages, including the Template Part fix.

This matters if your team patches by copying changed files, or reviews a diff before deploying. Use the full release package or your normal Composer update, not a hand-picked file list. Patchstack advises diffing the packages too.

Auto-updates and managed hosts

The release post says sites with automatic background updates will update on their own. That is true for many sites, but not all. Hosts, plugins and settings can turn it off. Sites where Composer or a Git deploy controls core files update when your pipeline runs, not on WordPress’s schedule.

Hosts differ in how they roll out the release:

  • Pantheon. Its WordPress 7.1.5 release note says to apply the update from the dashboard or with Terminus. Pantheon deployed firewall (WAF) protection in advance for some of the issues. It adds, "The WAF rules do not replace the update, so update your sites as soon as possible."
  • Other managed hosts. Many apply core security releases for you, but timing varies. Check your host’s status page or ask support. Our guide to choosing a managed WordPress host covers what to ask.

What to check on every client site

1. Confirm the version. Each site should show WordPress 7.1.5 or its branch’s fixed release under Dashboard, then Updates. With WP-CLI, wp core version prints the installed version.

2. Check core files. The wp core verify-checksums command "Verifies WordPress files against WordPress.org’s checksums." Run it after the update to catch partial updates or changed files.

3. Ask about custom queries. Have your developers search custom themes and plugins for meta_query built from request data. Even after the core fix, that pattern deserves a review.

4. Decide on XML-RPC. If a site does not use XML-RPC for apps or remote publishing, consider blocking it at the server or firewall. Test first, since some plugins rely on it.

5. Review accounts. List every Contributor, Author and Editor. Remove the ones nobody uses. On multisite, review who holds site Administrator rights.

6. Look at comments. On sites with the Latest Comments block, check recent comments for odd shortcode markup before you approve more.

If one site looks compromised, our post on why cleaned WordPress sites get reinfected covers the cleanup order. Our guide to reading a plugin vulnerability report helps with the plugin side.

What we do not know yet

As of November 20, 2026, WordPress has not published CVE IDs for these fixes. Patchstack says none had been assigned when it published. WordPress does not publish severity scores in its release post.

Neither WordPress nor Patchstack reports that any of these bugs are being exploited. That can change quickly after a release, because attackers can compare the old and new code.

Frequently Asked Questions

What is WordPress 7.1.5?

A security release that shipped on November 18, 2026. It fixes 18 vulnerabilities and adds two hardening changes. WordPress recommends updating right away.

Which WordPress 7.1.5 fix is the most serious?

The privilege escalation through Template Part block attributes. It needs no login, and WordPress says it could lead to remote code execution. Patchstack says someone who can open the crafted content has to open it.

Is anyone exploiting these bugs?

As of November 20, 2026, neither WordPress’s release post nor Patchstack’s analysis reports exploitation. Patch anyway, since the fixes are now public.

My site updates automatically. Do I need to do anything?

Confirm that the update ran. Background updates can be turned off by a host, a plugin or a setting. Sites managed with Composer or Git update only when your pipeline runs.

Which version should a site on an older branch show?

For example, 7.0.9 on the 7.0 branch, 6.9.12 on 6.9 and 6.8.13 on 6.8. HelpHub lists fixed releases for every branch back to 4.7.40.

Does WordPress 4.6 get this fix?

No. WordPress 4.6 and earlier no longer receive security updates. Sites that old need a full upgrade plan.

We run multisite. What should we check?

Update first. Then review who holds site Administrator rights, since one fix stops a site Administrator from taking over a Super Admin account.

Does a host firewall protect us until we update?

Partly, at best. Pantheon says it added WAF rules for some of the issues, and that they do not replace the update. Ask your own host what it covers.

Do the fixes reach WordPress 7.2?

Yes. The release post says WordPress 7.2 RC2 shipped with the fixes that apply. The final 7.2 release is planned for December 8, 2026.

Digital Matters

Security Desk