Stuart Neal
Director of Operations at Nextgen Marketing
We have worked with Vitalli and his team for well over a year now and will continue to do so in the future.
Having the confidence in an agency that allowed us to scale up and down development resources, as and when needed, has really made a positive difference to our agency.
Home / Blog / News / WordPress 7.1.5 ships 20 security fixes, including an unauthenticated path to RCE
WordPress.org published the 7.1.5 release announcement on 18 November with the sentence every agency should read as a work order: because this is a security release, it is recommended that you update your sites immediately. Twenty security entries, several of them reachable without an account, and a release cadence that now puts a security update on the calendar roughly every three weeks — 7.1.4 shipped on 28 October, 7.1.5 exactly three weeks later. That rhythm is the real story for anyone running more than a handful of sites, and it is the argument for a maintenance arrangement that turns a release like this into a scheduled task rather than an interruption.
The remaining entries are lower severity but worth knowing, because they describe what a logged-in user can do that they should not be able to: Author+ disclosure of user email addresses through the REST API comments endpoint, Editor+ disclosure via post and template author assignment, Subscriber+ disclosure through `wp.getComments` over XML-RPC, an Author+ authorisation bypass in comment editing, and a series of stored XSS issues at Contributor and Administrator level — the Comment Date block’s date format, oEmbed provider responses, Openverse image metadata, media filenames when converting a media block to a File block, and Customizer previews. Two entries are hardening rather than exploitation: a malformed regular expression that broadened JSON media type matching, and the removal of the block editor’s Imgur embed variation, whose server-side provider no longer exists.
Reporters include Anthropic on two of the twenty, alongside six members of the WordPress Security Team. The release was led by Jeremy Felt, Jerry Jones and Jarda Snajdr.
If your sites sit on one of our maintenance plans, 7.1.5 is already handled — applied, checked and logged, and it will appear as its own line in your next monthly maintenance report with the date it went on. There is nothing for you to do here. If you are not on a plan, this is precisely the scenario one is built for: a twenty-item security release landing on a Wednesday, with at least one issue that does not require an attacker to have an account on the site.
Source: WordPress.org