Source: wordpress Version: 7.1.3+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
Hi Craig, https://wordpress.org/news/2026/10/wordpress-7-1-4/ lists a batch of security fixes applied (likely affecting as well the other older series): - A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram. - A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.). - Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic. - Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team. - A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team. - A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.). - A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team. - Specially crafted User Logins can lead to a stored XSS reported by Anthropic. - Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban. - A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. - Stored XSS in core/comments-pagination-next and core/comments-pagination- previous blocks, reported by Alex Concha of the WordPress Security Team. - Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. - An update to the bundled root certificates due to the eMudhra revocation. Regards Salvatore
