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 ones that matter most

  • Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka. No login required, ends in code execution — this is the one that sets the urgency for the whole release
  • Multisite privilege escalation letting a site Administrator take over a Super Admin account through Customizer menu previews, reported by Yuval Miller. If you run multisite for a client network, your per-site admins just became a bigger trust decision
  • SQL injection in `WP_Meta_Query` via nested relation values, reported by Christiaan Swiers
  • SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team
  • Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad of Awesome Motive
  • Unauthenticated information disclosure exposing private taxonomy terms through the REST API search endpoint, reported by Anthropic
  • Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo

The rest of the list

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.

What agencies should do this week

  • Update every site to 7.1.5, or confirm that automatic background updates already applied it — do not assume, check
  • Multisite installs deserve a second look given the Super Admin takeover path
  • If a client site is on a deliberately delayed update policy, this is the release to make an exception for. An unauthenticated route to RCE does not wait for your next maintenance window
  • Older branches are covered: the fixes were backported to every branch still eligible, currently as far back as 4.7, and will ship as they become ready. That matters if you have inherited a site nobody has dared to upgrade
  • 7.1.5 is a short-cycle release. The next major version, 7.2, is planned for 8 December, so there is no “we will catch it in the next one” argument available

What this means for Codelibry clients

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

Vitalii Omelchenko
Founder at Codelibry and WordPress enthusiast. Helping digital agencies to protect their margins and do better at website delivery.Need help with wordpress builds? Book a call using the Contact page
our Blog

Explore our Latest Insights

WordPress core landed on the US actively-exploited list four times in 2026. It had never been there before
News
November 20, 2026
PHP shipped 18 CVEs worth of fixes this week. Two of them reach an ordinary WordPress site
News
November 20, 2026
Two critical NGINX HTTP/2 flaws can reach code execution. Updating WordPress will not help
News
November 20, 2026
whatsapp icon