ForgeNEX

WordPress 7.1.5 fixes 20 flaws: unauthenticated RCE and critical SQL

WordPress releases version 7.1.5 and closes 20 vulnerabilities, including an unauthenticated remote code execution and two SQL injections. Update now.

4 min read

In this article

WordPress has released version 7.1.5, a patch that closes 20 security issues in the core of the content manager. This is not a minor update: among the fixed flaws there is a remote code execution that does not require having an account on the site and two SQL injections. If your SMB has a WordPress website, or if you manage several, this affects you directly.

The most serious flaw: unauthenticated RCE in the Template Part block

The most significant problem is located in the Template Part block, the one WordPress uses for shared elements such as headers and footers. It was reported by researcher Logan Homolka and allowed an unauthenticated attacker to obtain permissions that did not correspond to them and, under certain configurations, to execute code on the server.

The official announcement does not detail which configurations were exposed or whether any attack that exploited it has been detected. That lack of specificity is not reassuring: in security, silence about active exploitation does not mean it does not exist. If your website uses custom blocks in the header or footer, this is the flaw that should worry you most.

Illustrative detail: WordPress fixes 20 security issues, with risk of remote code execution

Multisite: from site administrator to Super Admin of the entire network

The second most serious flaw affects Multisite installations, the feature that allows managing several websites from the same panel. Yuval Miller reported an error that allowed an administrator of a specific site to take over a Super Admin account, the profile that controls the entire network and not just an individual website.

The difference is relevant if you manage a network with several sites: whoever controls a Super Admin can access every installation in the network, not an isolated one. For an SMB with several brands, languages or locations under the same WordPress, this turns a local flaw into a global compromise.

Two SQL injections and several XSS

The patch also fixes two SQL injection flaws. Christiaan Swiers detected one in WP_Meta_Query, the function that builds database queries from metadata. Rudy Faile, a member of the WordPress security team, found the second, related to cover previews in the Customizer. An injection of this type can alter how the database interprets a query, which opens the door to reading or modifying data you should not be able to see.

To this are added several cross-site scripting (XSS) vulnerabilities, which allow executing a script in another user's browser without you noticing. One of them, of the persistent type, affects comments and does not require having an account on the site. The rest of the XSS fixes cover the legacy media library, embeds and the block editor.

Data leaks and other closures

The package also closes a leak that exposed private taxonomy terms (categories or tags) through the REST API search without the need to log in. In addition, it fixes a denial-of-service flaw related to XML-RPC pingbacks and a privilege escalation in comment editing.

Among the 20 entries there are two preventive changes: stricter checks on the JSON content type and the removal of an Imgur embed option whose provider no longer existed.

What it means for an SMB and what we recommend doing

WordPress recommends updating immediately, and at ForgeNEX we agree: there is no reason to wait. But updating is the first step, not the only one. Our recommendation for IT teams and SMBs with a web presence:

  1. Update the core to 7.1.5 as soon as possible, in all environments, including staging ones that are exposed.
  2. Review the plugins that use custom taxonomies, because they are the ones that rely most on that REST query that was exposed.
  3. If you have Multisite, audit the Super Admin profiles and confirm who has access and from where.
  4. Check whether you use custom blocks in the header or footer and review the server logs in case there was anomalous activity prior to the patch.
  5. Do not stop at the core: templates, plugins and PHP versions are also part of the attack surface.

This case fits a pattern we have been seeing: flaws do not always come through the main door, but through components we take for granted. Something similar happened with the seven Ruby flaws in regex and strings, where five allowed code execution. The lesson is the same: keeping what supports your website up to date is not optional, and it is advisable to have a process, not just good will.

An outdated website is not just a technical risk: it is an open door to the loss of customer data and business interruption.

If you are not sure where to start, at ForgeNEX we can help you review the status of your WordPress, prioritize patches and establish a maintenance plan. Security is not improvised; it is planned.

Source: RedesZone. Analysis and adaptation: ForgeNEX.

Keep reading

Call us WhatsApp