Retraceur 4.7.0: security and maintenance release

Publié le

dans

.
Un sauveteur marche en bord de mer

Retraceur 4.7.0 is a maintenance and security release: it brings in the fixes of yesterday’s WordPress® 7.1.5 release, backported onto the WordPress® 7.0 branch. used by the 4.0 branch. As a result Retraceur 4.7.0 is synced with WordPress® 7.0.9. Updating right away is strongly recommended.

What is fixed

WordPress® lists about twenty vulnerabilities in its announcement. For Retraceur, the fixes fall into these families:

  • SQL injection. WP_Query and WP_Meta_Query now validate the values they receive more strictly, notably the nested relations of meta queries.
  • XSS. Several outputs are better protected: the Interactivity API store namespace, shortcode attributes, oEmbed provider responses, and the file name used when converting a media block into a File block in the editor.
  • Information disclosure. The REST API no longer exposes private taxonomy terms through search, and assigning an author to a post or a template is better controlled.
  • Hardening. A malformed regular expression for JSON media types is fixed, the “front page” option is sanitized, the Imgur embed variation is removed from the editor, and the editor now rejects unsafe entity keys before calling the REST API.

Good news along the way: several of the vulnerabilities announced by WordPress affect features that Retraceur no longer ships (Customizer, Multisite, XML-RPC, Comments, Openverse). They don’t apply to you.

Two Retraceur-specific fixes

  • In the Blocks administration, the single-row “Delete” links now use the correct nonce.
  • The database version number, missed when 4.0.0 was released, is fixed. This avoids errors in future major upgrades, which would replay an operation on indexes that had already been altered. A one-time database update may therefore run after installing 4.7.0.

How to update

Go to the Updates screen in your administration, or use the button below download the .zip archive file before manually updating your website.

Thanks to the WordPress® security team nd everyone involved in identifying, reporting and fixing these vulnerabilities.

Featured photo: Photo de Frames For Your Heart on Unsplash

Note: The WordPress® trademark is the intellectual property of the WordPress® Foundation. The use of the WordPress® name in this article is for identification purposes only and does not imply endorsement by the WordPress® Foundation.