WordPress Development Team Unveils Security Release 7.1.5
On November 18, the WordPress development team announced the release of “WordPress 7.1.5,” a security-focused update for its renowned website-building platform.
This significant update rectifies 20 vulnerabilities present in the core software. The team strongly advises all administrators of active sites to execute the update without delay.
This release follows closely on the heels of version 7.1.4, which debuted three weeks prior, reflecting a concerted effort toward rapid security enhancements.
The foremost critical fix within this update addresses a privilege escalation vulnerability linked to the “Template Part” block attributes.
This flaw has the potential to be weaponized by unauthenticated third parties, potentially leading to remote code execution (RCE), which could facilitate a complete site takeover or permit the execution of harmful code on the server. Given the severity of this issue, administrators have been cautioned to act since the public release.
The array of 20 fixes encompasses various critical security categories, such as privilege escalation, cross-site scripting (XSS), information disclosure, unauthorized access, denial of service (DoS) vulnerabilities, and systemic hardening enhancements.
Notably, two SQL injection flaws were identified: one pertains to “WP_Meta_Query,” which manages search conditions for custom fields, while the other is associated with the front-page settings within the customizer’s changeset preview.
The release also mitigates challenges pertinent to multisite environments. It rectifies a privilege escalation vulnerability that enabled a site administrator to commandeer a Super Admin account via the customizer’s menu preview.
This is particularly alarming for large-scale installations hosting multiple sites, as the ramifications can extend beyond typical administrative privileges.
The principal fixes are impressively diverse.
- Privilege Escalation: Unauthenticated escalation via Template Part block attributes; Super Admin takeover in multisite setups.
- SQL Injection: Nested relation values in WP_Meta_Query; vulnerabilities in front-page settings within the customizer’s changeset preview.
- XSS: Various issues, including a reflected XSS within the legacy media library popup and an unauthenticated stored XSS via comment shortcode attributes.
- Information Disclosure: Leakage of private taxonomies through the REST API search endpoint; leakage of email addresses from the comments endpoint.
- Denial of Service: Unauthenticated DoS through bulk XML-RPC pingback dispatch.
- Hardening: Correction of an erroneous regular expression in JSON media-type detection; elimination of a variation in Imgur embed.
Note: The fixes are organized according to details disclosed in the official release announcement. At the time of writing, CVE numbers and severity ratings were not available in the main source.
In terms of implementation, these fixes are being backported to all branches eligible for security updates, with current coverage extending to versions down to 4.7.
Releases will be distributed as they are finalized. For sites with automatic background updates enabled, the process will initiate automatically, while those lacking this feature can manually apply the update via the “Updates” screen in their dashboard.
The WordPress team also emphasized its policy of actively supporting only the latest version of the software.
Additionally, a prior modification in “WordPress 7.0,” which removed 1024-bit certificates from the bundled root certificates, has now been applied retroactively to versions 6.9.12 and earlier. Environments still operating on obsolete versions are encouraged to review their certificate-related behaviors.
The forthcoming major version, “WordPress 7.2,” is presently in release candidate (RC) status, with a public release anticipated on December 8. Noteworthy fixes from this release have already been integrated into “WordPress 7.2 RC 2.”
Since the release of version 7.1.4 on October 28, WordPress has been under heightened scrutiny due to a vulnerability that targeted sites during core updates.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) registered this exploit on November 3, confirming its use in actual attacks.
This series of events underscores the fact that the update process itself can serve as a potential entry point for attackers, and administrators are urged to perform updates both promptly and systematically.
The latest announcement does not indicate that any of these vulnerabilities have been actively exploited. CVE identifiers had yet to be assigned to these issues at the time of writing.
Nonetheless, given the potential for unauthenticated privilege escalation to evolve into RCE, live sites should prioritize implementing the necessary patches.
In particular, environments where updates are managed manually and those configured as multisites hosting numerous sites must urgently identify any lapses in security measures.
Source link: Finance.biggo.com.




