Administrator checking a security update on a laptop while following WordPress news Administrator checking a security update on a laptop while following WordPress news

WordPress news: 7.1.5 ships a wide-ranging security fix

WordPress 7.1.5, released November 18, contains security fixes and hardening changes across core. The project recommends updating sites immediately and says backports for eligible branches are in progress.

WordPress 7.1.5 was released on November 18 as a security update, and the project recommends installing it immediately. This WordPress news matters to site owners and developers who need to know what changed, whether older branches are included, and where to apply the update.

The release notes list a wide range of issues, from privilege escalation and SQL injection to cross-site scripting (XSS) and information disclosure. They also describe hardening changes. Here is what the project has confirmed and what site administrators can do next.

What WordPress 7.1.5 changes

The WordPress announcement calls 7.1.5 a short-cycle security release. It does not assign severity scores to the listed issues, so the notes are best read as a list of fixes rather than a ranked risk assessment. The project’s advice is direct: update sites immediately.

Among the issues described are a multisite privilege escalation that could let a site Administrator take over a Super Admin account through Customizer menu previews, and an unauthenticated privilege escalation involving Template Part block attributes that could lead to remote code execution. The announcement also lists SQL injection involving nested relation values in WP_Meta_Query and Customizer front-page setting previews.

Several fixes concern data exposure. The release addresses unauthenticated disclosure of private taxonomy terms through the REST API search endpoint, Author-level access to email addresses through the REST API comments endpoint, and information disclosure through XML-RPC and REST API routes. These are distinct issues with different access conditions, as described in the release notes.

WordPress news: XSS fixes cover several areas

The release also lists XSS fixes in the block editor, Customizer previews, comments, the legacy media library popup and oEmbed provider responses. Two block-editor issues have specific input paths: Openverse image metadata, and media filenames when converting a media block to a File block. The notes identify the latter as a stored XSS issue affecting users at Contributor level or higher.

Other entries include an XSS issue in the Interactivity API context function and a stored XSS issue involving the Comment Date block’s date format. The release also addresses unauthenticated denial of service through batched XML-RPC pingbacks and an Author-level authorization bypass for comment editing in the admin.

Two changes are described as hardening rather than as a conventional vulnerability fix. WordPress corrected a malformed regular expression that broadened JSON media-type matching, and removed the block editor’s Imgur embed variation because its server-side provider is no longer available.

How to install the security update

Site owners can install WordPress 7.1.5 from the dashboard by opening Updates and selecting Update Now. The release announcement also provides a download from WordPress.org. Sites that support automatic background updates will begin updating automatically, according to the project.

The announcement recommends immediate updates but does not give a separate manual procedure for hosts, multisite networks or custom deployment pipelines. If you manage sites through a controlled release process, check that the new version is applied there and confirm the site’s update status afterward. That is a general operational step, not a special requirement stated in the release notes.

Backports are in progress for older branches

WordPress says it is backporting the security fixes to branches eligible for security updates, currently through version 4.7. Those backports are still in progress and will ship as they become ready. The project also reminds users that only the most recent WordPress version is actively supported, so an older site should not assume its branch has already received every fix.

The post includes a separate compatibility detail: the removal of 1024-bit certificates from bundled root certificates, previously made in WordPress 7.0, has been applied to 6.9.12 and earlier as part of this release. WordPress also says that 7.2 RC 2 contains all applicable fixes. The announcement does not provide a separate release date for the backports in its text.

FAQ

Should I update to WordPress 7.1.5 now?

Yes. WordPress describes 7.1.5 as a security release and recommends updating sites immediately. Install it through the dashboard or your established update process.

Does WordPress 7.1.5 include fixes for older branches?

The project says backports are in progress for eligible security branches through 4.7. They will ship as they become ready, so check for the update applicable to your branch rather than assuming it is already available.

Is WordPress 7.2 RC 2 affected by these issues?

The release announcement says WordPress 7.2 RC 2 contains all applicable fixes. WordPress 7.2 is still a release candidate, so the announcement’s recommendation for sites is to install the stable 7.1.5 update.

Next step: check the Updates screen on each WordPress site you manage and apply 7.1.5 where it is available.

Leave a Reply

Your email address will not be published. Required fields are marked *