Security release · WordPress Core · 19 November 2026

WordPress 7.1.5: twenty security fixes, and which ones matter first

WordPress 7.1.5 came out on 18 November 2026, three weeks after 7.1.4. It is a security-only, short-cycle release with twenty fixes: eighteen vulnerabilities and two hardening changes. WordPress recommends updating immediately. The most serious fix closes an unauthenticated privilege escalation through Template Part block attributes, which WordPress says can lead to remote code execution and WPScan rates CVSS 8.8. It also closes a SQL injection in WP_Meta_Query, a stored XSS that an anonymous commenter can plant, and an XML-RPC denial of service that needs no account. On multisite, a site Administrator could take over a Super Admin account. Fixes were backported to every branch down to 4.7, as 7.0.9, 6.9.12 and so on down to 4.7.40. No CVE numbers had been assigned when the release went out. No exploitation or public proof of concept had been reported by 19 November. This page sorts the twenty fixes by who can use them and gives the checks to run after updating.

Released
18 November 2026, a short-cycle security release; WordPress 7.2 is planned for 8 December and 7.2 RC2 carries the same fixes
Fixed
20 items: 18 vulnerabilities and 2 hardening changes. Six need no account, though four of those also need a logged-in victim, a particular block or a plugin
Backports
7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12, 6.5.15 down to 4.7.40; 4.6 and earlier get no security fixes
Severity
No CVEs assigned at release. WPScan rates the Template Part privilege escalation CVSS 3.1 8.8 (High)
Exploitation
None reported, and no public proof of concept, as of 19 November 2026
Also update
The Gutenberg plugin, where it is active, to 24.4.2 or later

Start here

Twenty fixes, sorted by who can use them

The release post lists each fix by name and reporter, with no CVE number or severity score. Patchstack’s write-up adds a column that matters more to a site owner than a score: what an attacker needs before the flaw is any use. Sorted that way, the twenty fixes fall into four groups. The first group needs no account. The second needs a site Administrator on a multisite network. The third needs a low-privilege login such as Contributor, Author or Subscriber. The fourth is hardening with no exploitable path.

Two of the unauthenticated issues start with an anonymous visitor and end in a logged-in user’s browser. The Template Part flaw is the more serious. A template part is addressed by a theme//slug key taken from the block’s own attributes, and before 7.1.5 the editor joined that key into REST API paths without checking it. A crafted key can therefore point the editor at an endpoint the attacker chose, and the request goes out with the logged-in user’s cookies and nonce. WordPress says this can lead to remote code execution. Patchstack notes that the code change on its own shows the path injection, and that the step to code execution would be the administrator’s own plugin-installation endpoints. The sources disagree on who has to open the content: Patchstack says an editor user, WPScan says an administrator visiting a crafted link. Neither explains how an attacker without an account gets the block in front of them.

The other is a stored XSS through shortcode attributes in comments. Comments are filtered when they are saved, and a comment with no < or > passes the filter untouched. shortcode_parse_atts() then turned escapes such as \x3c back into < after the filter had run. The script runs only on a page that has the core Latest Comments block, because that block renders comment excerpts where shortcodes are processed. The SQL injection in WP_Meta_Query is listed as unauthenticated too, but it is reachable only through a plugin or theme that passes request data into a meta_query. Core alone does not expose it.

Figure 1 · WordPress 7.1.5 at a glance

Twenty fixes, six that need no account, none exploited yet.

QuestionWhat the sources sayWhat to do
Scope18 vulnerabilities and 2 hardening changes in one releaseUpdate Core on every site this week
Worst flawTemplate Part privilege escalation that can lead to RCE, CVSS 8.8Update Gutenberg to 24.4.2 where it is active
No account neededSix fixes, including SQL injection, comment XSS and an XML-RPC DoSSearch comments for escaped markup after updating
MultisiteA site Administrator could take over a Super AdminRun wp super-admin list and check every address
Patch7.1.5 and backports from 7.0.9 down to 4.7.40Confirm the version; do not assume auto-update ran
ExploitationNone reported, no public PoC, no CVEs yetUpdate calmly, but this week
What WordPress.org, Patchstack and WPScan published about WordPress 7.1.5, and what each item means for a site owner or agency.
Who can use itFixesWhat it means for a site
Nobody logged inTemplate Part privilege escalation that can lead to RCE (a logged-in user must open the content); stored XSS through comment shortcode attributes (needs a Latest Comments block); SQL injection in WP_Meta_Query (needs a plugin or theme that passes request data into a meta query); private taxonomy terms exposed through the REST API search endpoint; denial of service through batched XML-RPC pingbacks; reflected XSS in the legacy media library popup (a user who can upload must click a link)Every public site. Update first; these are the fixes an attacker can try against a site without having any access
A site Administrator on multisiteTakeover of a Super Admin account through Customizer menu previews; SQL injection through the front page setting in Customizer changeset previews; stored XSS through Customizer previewsNetworks where site Administrators are not fully trusted, such as client sites, schools or franchises. An Administrator of one site could reach the whole network
A Contributor, Author, Editor or SubscriberContributor+ stored XSS through oEmbed provider responses, the Comment Date block’s date format, and media filenames converted to a File block; Author+ comment editing beyond their rights and exposure of user email addresses through the REST comments endpoint; Editor+ exposure of user details through REST author assignment; Subscriber+ exposure of commenter email and IP addresses through XML-RPC wp.getCommentsSites with open registration, guest authors, members or many staff logins. Script stored by a Contributor can run when an administrator views the post
Content or code the attacker does not control directlyXSS through Openverse image metadata (an editor must insert the image); XSS in wp_interactivity_data_wp_context() (a plugin or theme must pass untrusted input as the store namespace)Low on its own; each needs an editor’s action or a third-party mistake to complete
Hardening onlyA malformed regular expression that matched more JSON media types than intended; removal of the block editor’s Imgur embed variation, whose provider no longer existsNo exploitable path described; they ship with the update

Versions

The fixed version for each branch

WordPress backported the fixes to every branch that still gets security releases, down to 4.7. The HelpHub page lists the versions below. Older branches carry fewer of the twenty fixes because they do not contain the affected code, not because they were skipped. The release post said on 18 November that backports were still in progress and would ship as they became ready, so check the version a site actually installed.

Two further changes ship with this release. The Gutenberg plugin carries its own copy of the block-editor packages, so on a site where it is active the plugin’s code is what runs; WPScan lists the Template Part flaw as fixed in Gutenberg 24.4.2. And the 6.9.12 and older releases also remove 1024-bit certificates from the bundled root certificate list, as WordPress 7.0 already did. That is not a security fix. It can only matter to a site on an old branch that talks to a server still using such a certificate.

Patchstack points out that the documented file list covers the PHP changes, while five of the twenty fixes, including the Template Part one, arrive through updated JavaScript packages. Use wp core verify-checksums to confirm a site’s files match the release, rather than comparing against the documented list.

BranchFixed inFixes that apply
7.17.1.5All 20
7.0 down to 6.57.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12, 6.5.15All 20
6.4 down to 6.26.4.15, 6.3.15, 6.2.1619
6.1 and 6.06.1.17, 6.0.1918
5.95.9.2117
5.8 down to 5.65.8.20, 5.7.22, 5.6.2415
5.5 down to 5.15.5.25, 5.4.26, 5.3.28, 5.2.31, 5.1.2913
5.0 down to 4.85.0.32, 4.9.36, 4.8.3512
4.74.7.4011
4.6 and earlierNoneNo longer receive security updates

After updating

What to check once the update is in

Nothing in this release has been reported as exploited, so these checks are a short review, not incident response. They cover the three fixes whose effects would outlast the update: a Super Admin taken over on multisite, script left behind in a comment, and block markup left behind for an editor to open. The commands are read-only.

  1. 01

    Confirm Core and the files

    On every site, staging copy and replica, with plugins and themes skipped so a broken plugin cannot hide the result:

    WP-CLI
    wp core version --skip-plugins --skip-themes
    wp core verify-checksums --skip-plugins --skip-themes
    wp plugin get gutenberg --field=version

    The first should print 7.1.5 or your branch’s release from the table above. Read the output of verify-checksums rather than its exit code, which can be 0 with warnings. The last command matters only where Gutenberg is installed; it should print 24.4.2 or later.

  2. 02

    On multisite, review the Super Admins

    A site Administrator could take over a Super Admin account before this release. List the accounts that hold network rights and the email address on each:

    WP-CLI
    wp super-admin list
    wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --url=<site>

    Each Super Admin should be someone you know, with an email address you recognise. An account whose address changed recently is the sign to look for, because a takeover usually works by changing the address or password of an existing account rather than creating a new one.

  3. 03

    Look for escaped markup in comments

    The stored XSS hid < and > as escapes such as \x3c, so search approved and pending comments for them:

    WP-CLI
    wp comment list --status=all --search=x3c --fields=comment_ID,comment_post_ID,comment_author,comment_date
    wp comment list --status=all --search=x3e --fields=comment_ID,comment_post_ID,comment_author,comment_date

    A real comment rarely contains these strings. A hit inside a shortcode attribute is the payload: delete the comment. 7.1.5 stops it from running, but it should not stay on the site.

  4. 04

    Look for template-part blocks outside templates

    Template part blocks belong in templates and template parts. One in a post, page or comment is worth a look:

    WP-CLI
    wp db query "SELECT ID, post_type, post_status, post_author, post_modified FROM $(wp db prefix --skip-plugins --skip-themes)posts WHERE post_content LIKE '%wp:template-part%' AND post_type NOT IN ('wp_template', 'wp_template_part', 'revision')" --skip-plugins --skip-themes

    Synced patterns (post type wp_block) can contain template parts legitimately. For anything else, open the post in the code editor and check that the block’s slug and theme attributes are plain names with no dots, slashes, question marks or percent signs.

  5. 05

    Check XML-RPC traffic

    The denial of service batched many pingbacks into one XML-RPC request. Find the addresses that post to xmlrpc.php most often:

    shell
    grep "POST /xmlrpc.php" /var/log/apache2/access.log | awk '{print $1}' | sort | uniq -c | sort -rn | head

    Adjust the log path for your server (on cPanel, /usr/local/apache/domlogs/<domain>). A few addresses with thousands of requests, together with slow PHP workers, is the pattern. If nothing on the site uses XML-RPC (the Jetpack plugin and some mobile and publishing apps do), deny it at the web server.

Actions

The actions, in priority order

Update first. The rest depends on whether the site runs multisite, takes comments, or has low-privilege accounts.

  1. 01

    Update Core on every site

    Update to 7.1.5 or your branch’s release from the Dashboard, the Updates screen or wp core update, and confirm the version afterwards. Keep the web-server rule that denies wp-content/upgrade/ in place: the update itself runs the upgrade code, which is what CVE-2026-119977 was about.

  2. 02

    Update Gutenberg where it is active

    The plugin replaces Core’s block-editor code. Update it to 24.4.2 or later, or deactivate it if the site does not need it.

  3. 03

    Review Super Admins on multisite networks

    List them with wp super-admin list, check each one’s email address, and remove anyone you cannot account for. Then ask whether every site Administrator on the network needs that role.

  4. 04

    Trim low-privilege accounts

    Seven fixes need a Subscriber, Contributor, Author or Editor account. Remove accounts nobody uses, and turn off open registration (Settings → General → Membership) if the site does not need it.

  5. 05

    If an update has to wait

    No vendor workaround was published. Two of our own stopgaps reduce exposure for a few days: hold comments for moderation (Settings → Discussion) and deny xmlrpc.php at the web server if nothing uses it. Neither covers the Template Part flaw or the multisite takeover, so do not let them delay the update.

Sources

Where every claim on this page comes from

The list of fixes, the reporters, the release date and the backport statement come from the WordPress.org release post of 18 November 2026, written by Jeremy Felt. The branch versions and the number of fixes in each come from the HelpHub page for 7.1.5. What each flaw requires, the Template Part and comment shortcode mechanisms, the Latest Comments condition, the note on the documented file list and the statement that no CVEs had been assigned come from Patchstack’s article of the same day. The CVSS 8.8 rating, the Gutenberg 24.4.2 fix and the administrator wording for the Template Part flaw come from WPScan’s entry; WPScan’s other entries give the meta query and XML-RPC descriptions. Two of the fixes were reported by Anthropic. The stopgaps in the actions are our own suggestions, not WordPress’s.

Where sources disagree, both are given. Patchstack says an editor must open the Template Part content; WPScan says an administrator must visit a crafted link. The release post says backports were in progress, while HelpHub lists them as released. Exploitation status is as of 19 November 2026. If that changes or CVE numbers are assigned, this page and the weekly briefing will say so.

Common questions

Common questions about WordPress 7.1.5

Is WordPress 7.1.5 being exploited?

Not as far as anyone has reported. As of 19 November 2026 no exploitation in the wild, no public proof of concept and no CISA listing had been reported for any of the twenty fixes. Two of the last three Core security releases, 7.1.2 and 7.1.4, each fixed a flaw that was exploited within weeks, so treat this as an update for this week.

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

Check that the update happened: wp core version, or the version shown at the bottom of the Dashboard. Then do the two things auto-update does not do: update the Gutenberg plugin if it is active, and on multisite, review the Super Admin list.

We are on an older branch, such as 6.8. Which version do we need?

The security release for that branch: 6.8.13 for 6.8, 6.9.12 for 6.9, 7.0.9 for 7.0, and so on down to 4.7.40. The full list is in the versions table. Older branches contain fewer of the twenty fixes because the affected code is not in them. 4.6 and earlier receive no security fixes, so a site on one of those needs a major upgrade.

Does the SQL injection mean anyone can read my database?

Not through Core alone. The WP_Meta_Query flaw is reachable without a login only when a plugin or theme passes data from the request into a meta query. That is a common pattern in search and filter plugins, so assume some sites are exposed and update; the fix is in Core, so it covers every plugin at once.

Should I disable XML-RPC?

If nothing on the site uses it, denying xmlrpc.php at the web server removes the pingback denial of service and a long-standing brute-force target. Jetpack and some mobile and publishing apps do need it. 7.1.5 fixes the denial of service whichever you choose.

Why are no CVE numbers given?

WordPress did not include any in the release post, and Patchstack says none had been assigned at publication. Scanners may report these issues by WPScan or Patchstack identifier for now. This page will add CVE numbers once they are published.

Choose the response path

Core is on 7.1.5 and you are not sure what reached the site first: choose the response path.

Many sites, one release

Get every site confirmed on 7.1.5, with Super Admins and accounts reviewed.

Best when you run several sites or a multisite network, cannot easily confirm which version each one is on, and want the Core version, the Gutenberg plugin, the administrator and Super Admin lists and the low-privilege accounts checked in one pass with a written result.

Something already looks wrong

A Super Admin you cannot account for, a comment carrying script, or a plugin you did not install.

Best when the checks above have turned up an account, a comment or a plugin that should not be there, and you want the compromise scoped, the persistence removed and the site returned to a trusted state rather than only the one item deleted.