Skip to content
cmsreviews.uk Data checked weekly

Blog

WordPress 7.1.5 ships 20 security changes with 7.2 due 8 December

· 6 min read · Tom Hartley

WordPress 7.1.5 went out on 18 November 2026 as a security release, and the project says to update immediately. It lists 20 security fixes and hardening changes. It is also a short-cycle release: the next major version, 7.2, is scheduled for 8 December 2026 and reached Release Candidate 1 on 17 November.

Patch first, then use the three weeks before 8 December to test plugins and themes against the RC, because the 7.2 developer notes change the REST API, the Abilities API, the block editor and jQuery in ways existing code may depend on.

Several fixed flaws needed no WordPress account to exploit

The WordPress 7.1.5 release announcement gives no CVE ids or severity ratings, so none appear here. It gives a required role for most issues, and several need none at all.

Unauthenticated issues include a privilege escalation through Template Part block attributes, which the project says may allow remote code execution, a stored XSS through shortcode attributes in comments, a denial of service through batched XML-RPC pingbacks, and exposure of private taxonomy terms through the REST API's search endpoint.

Two are SQL injection: one in WP_Meta_Query through nested relation values, the other through the front page setting in Customizer changeset previews. On multisite, a site Administrator could take over a Super Admin account through Customizer menu previews.

Most of the rest are XSS and information disclosure bugs that need a logged-in account, from Subscriber up to Administrator (for example XSS through oEmbed provider responses at Contributor level, or user emails exposed through the REST comments endpoint at Author level), plus an Author-level authorisation bypass in admin comment editing. No role is given for some, including a reflected XSS in the legacy media library popup, an XSS in wp_interactivity_data_wp_context() and an XSS through Openverse image metadata. Two entries are hardening: a regular expression that matched JSON media types too broadly, and removal of the block editor's Imgur embed variation, whose provider no longer exists.

Fixes are being backported to every branch still eligible for security updates, currently back to 4.7, and ship as each one is ready. Sites with background updates on get 7.1.5 automatically; otherwise update from the dashboard or by downloading it from WordPress.org.

Release Candidate 2 includes the security fixes

The 7.1.5 announcement says RC2 has since shipped with the applicable security fixes included. The 7.2 Release Candidate 1 post warns against running it on production and asks plugin and theme authors to finish testing and set "Tested up to" to 7.2.

On staging, wp core update --version=7.2-RC1 installs it. RC1 also updates PHPMailer, Requests, getID3 and sodium_compat, and 7.2 adds the Ipsum default theme, SVG icons across wp-admin and PHP 8.6 compatibility work.

Check the console for jQuery Migrate warnings

7.2 ships jQuery Migrate 3.6.0. The core team's dev note says the point is to surface deprecation notices in plugin and theme code for features jQuery 4 drops, before jQuery itself moves. The final step of the previous jQuery plan, turning Migrate off by default, was never completed.

ReleasejQuery changeStatus
7.2jQuery Migrate updated to 3.6.0In RC
7.3Latest jQuery, jQuery Migrate and jQuery UITentative, depends on test results
7.5 or 7.6jQuery Migrate disabled by defaultPlanned for end of 2027, depends on testing

On a 7.2 staging site, open the browser console and look for jQuery Migrate deprecation messages from your own scripts. Progress is tracked on Trac ticket #60478.

Revision responses drop unrevisioned meta in 7.2

The REST API dev note for 7.2 describes three changes and warns that the first two can break code that relies on the current response or parameter format.

Revision and autosave responses now contain only meta keys that are actually revisioned. Until 7.2 the endpoint sent back all REST-exposed meta keys of the parent post type as defaults or null, and the block editor's Visual Revisions feature (new in 7.0) wrote those values over the post's real meta on restore. One symptom was an unsynced pattern turning synced after a restore.

A plugin that stores meta on revisions needs the key registered with 'revisions_enabled' => true or added through the wp_post_revision_meta_keys filter, or the key vanishes from REST revision responses. Where a post type has no revisioned meta, meta is now an empty array rather than an object of defaults.

The comments endpoint's status parameter is now an array, so /wp/v2/comments?status=approve,hold works in one request. Code that compared $request['status'] to a string stops matching; the dev note suggests in_array() against (array) $request['status']. A new rest_allowed_cors_methods filter controls the Access-Control-Allow-Methods header; default output does not change.

How does the Abilities API validate input?

Abilities can now declare required_capabilities, checked with current_user_can() before any permission callback runs. If that list covers every call, the permission callback can be omitted, but only on 7.2, so plugins supporting older versions must keep theirs.

Input is now normalised, validated and sanitised against the ability's schema on both direct PHP calls and REST requests. A number schema turns an integer into a float, so is_int() checks break; use integer instead. Sanitisation failures return ability_invalid_input (HTTP 400 over REST) instead of falling back to the raw input, and code that calls check_permissions() directly must call prepare_input() first.

Rename __experimentalGroup to group in InspectorControls

The __experimentalGroup prop on InspectorControls is gone. It was stabilised as group in 6.2, with a deprecation warning naming 6.4 for removal. Code still passing the old prop renders its controls in the default panel, so an Advanced-panel control ends up among the block's ordinary settings. Renaming the prop fixes it, since group works from 6.2.

Also from the editor dev note: custom CSS on a block that its parent renders itself, such as a Navigation Link loaded from a menu post, used to be dropped on the front end. In 7.2 it is output, so check for old rules you no longer want.

Site teams patch production now and test RC2 on staging

Update production to 7.1.5 now, and check that any site still on an older branch has received its backport. Then put 7.2 RC2 on staging and work through the browser console for jQuery Migrate warnings, any plugin that stores meta on revisions, REST clients that filter comments by status, custom abilities, and custom blocks built before 6.2.