WordPress Introduces Version 7.1.5 to Mitigate 20 Security Vulnerabilities
On November 18, 2026, WordPress unveiled version 7.1.5, a crucial update designed to rectify 20 identified security vulnerabilities within its Core.
This latest patch addresses a serious flaw that could empower unauthorized users to execute code on compromised servers, alongside two SQL injection vulnerabilities and a significant weakness that might allow a single site administrator to commandeer an entire WordPress Multisite network. Immediate action to update is strongly advised by WordPress.
Security analyst Logan Homolka brought to light a critical flaw in the Template Part block utilized by WordPress for shared layout components—such as headers and footers.
This vulnerability could enable an unauthenticated assailant to escalate their permissions illicitly, potentially facilitating remote code execution (RCE).
Notably, the announcement did not mention any active exploitation of this flaw, nor did it detail specific site configurations that might permit such code execution.
Separately, the Template Part issue is distinct from a previously identified weakness in the update process, detailed in the WordPress 7.1.4 security release report.
Additionally, the new release tackles a different Multisite-related problem, reported by Yuval Miller, that poses a risk of allowing site administrators to seize control of a Super Admin account.
This distinction is paramount since a Super Admin possesses the ability to manage the entire network rather than merely a single site.
SQL Injection, XSS, and Data Exposure
Security researcher Christiaan Swiers has identified an SQL injection vulnerability withinWP_Meta_Query, which formulates database queries based on metadata.
Concurrently, WordPress security team member Rudy Faile has reported an additional flaw affecting front-page previews in the Customizer. SQL injection vulnerabilities are particularly perilous; they can manipulate how a database interprets a query.
It is essential to note that these issues are independent of the export-related vulnerabilities addressed in WordPress 7.1.3.
Additional patches have been implemented to counter cross-site scripting (XSS) vulnerabilities, which could allow attackers to execute malicious scripts in the browsers of unsuspecting users.
One of these stored XSS vulnerabilities is particularly concerning as it pertains to comments and does not require user authentication.
Further modifications include enhancements to the legacy media library, embeds, and the block editor. The update also rectifies a data leak that previously exposed confidential taxonomy terms, such as categories or tags, via REST API searches without requiring a login.
The official release announcement from WordPress also outlines a denial-of-service vulnerability associated with XML-RPC pingbacks and a permissions bypass concerning comment editing.
The comprehensive list of 20 entries includes two preventive enhancements: more stringent checks for JSON content types and the removal of an Imgur embed option following the provider’s discontinuation of service.
Steps to Update WordPress
To initiate the update, navigate to Dashboard → Updates → Update Now, then confirm the successful installation of the latest version.
For sites equipped with automatic background updates, the patch will be applied without manual intervention; however, administrators are still encouraged to verify the update’s successful installation.
For legacy deployments, the WordPress 7.1.5 documentation specifies the patched versions associated with various branches, which include versions 7.0.9, 6.9.12, and 4.7.40.
It is critical to note that WordPress 4.6 and earlier versions are no longer eligible for security updates.
Minor patches for older branches are available to provide administrators a means of addressing these vulnerabilities if immediate upgrades to version 7.1.5 are not feasible; however, WordPress emphasizes that only the latest version receives active support. Furthermore, WordPress 7.2 Release Candidate 2 encompasses the necessary fixes.

The finalized release of version 7.2 is slated for December 8, yet site proprietors are strongly urged to implement the available security update without delay.
Source link: Cybersecuritynews.com.


