WordPress released version 7.1.5 on November 18 to fix security flaws including an account-free attack involving Template Part block attributes. An editor must open the malicious content for that attack to work, according to Patchstack's analysis. WordPress says the flaw allows privilege escalation and could lead to remote code execution.

The project recommends immediate updates in its release announcement. Patchstack counts 20 fixes, distinguishing 18 vulnerabilities from two hardening changes. WordPress 7.1.5 is available with security fixes, and SDAC recommends immediate installation.

The update follows version 7.1.4, which Patchstack reports fixed 17 issues three weeks earlier. Six of the new fixes concern access available to accounts with Contributor or higher privileges, giving the release implications for sites with multiple publishing roles.

WordPress 7.1.5 Closes the Template Part Attack Path

Patchstack describes the Template Part issue as REST path injection: attacker-controlled values redirect requests made with a logged-in editor's credentials. In plain English, the attacker can change where the editor's browser sends an authenticated request.

Other fixes address different access levels. In multisite installations, a site administrator could take over a Super Admin account through Customizer menu previews, WordPress says. The release also patches unauthenticated denial of service through batched XML-RPC pingbacks.

SQL injection, which lets malicious input alter database queries, is patched in WP_Meta_Query's nested relation values and the front page setting in Customizer changeset previews. Patchstack says the WP_Meta_Query issue requires code that passes request data into meta_query, tying exposure to how that functionality is used.

Cross-site scripting fixes span comments, media interfaces, Customizer previews and block editor features. One stored-XSS issue involving comment shortcode attributes requires a page containing a Latest Comments block, Patchstack reports. Five fixes arrive through a Gutenberg package update rather than the core PHP backport.

Where the Installed Version Appears

The installed WordPress version appears at the bottom of the Dashboard's At a Glance widget, according to the project's Dashboard documentation. WordPress 7.1.5 can be installed through Dashboard > Updates, WordPress says. Eligible sites also begin receiving the release through automatic background updates.

The one-click update process uses the Update Now button, according to WordPress. Installation temporarily puts the site into maintenance mode. WordPress recommends backups and compatibility checks before installation. The update page must remain open until installation finishes, WordPress says.

The release's different access requirements also make account roles and enabled features relevant to understanding exposure.

Older Branches Receive Different Patched Versions

Patched releases for older branches include 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12 and 6.5.15, according to WordPress. Each of those branches is affected by all 20 listed issues.

Further back, branch 4.7 is affected by 11 of the 20 issues and receives version 4.7.40. WordPress says backports extend through 4.7 and are shipping as they become ready. Versions 4.6 and earlier no longer receive security updates.

These courtesy patches preserve an update route for older installations, while WordPress continues to identify only its newest version as actively supported. Receiving a particular security fix therefore does not put an older branch on the same support footing as the newest release.

For more on this topic, see our Technology coverage.

Image: AI-generated image.