Web Hosting

WordPress 7.1.5 Security Release: Multisite, REST and XSS Fixes

Two padlocks on an old door, a stand-in for the WordPress 7.1.5 security release

As of 2026-11-19 UTC. The WordPress 7.1.5 security release was published by WordPress.org on November 18, 2026. Primary source: WordPress 7.1.5 Release.

What shipped in the WordPress 7.1.5 security release

The WordPress 7.1.5 security release went out on November 18, 2026, led by Jeremy Felt, Jerry Jones, and Jarda Snajdr. WordPress.org describes it plainly: “This security release features fixes for multiple issues.” The announcement follows with a direct instruction: “Because this is a security release, it is recommended that you update your sites immediately.”

WordPress.org also calls it a short-cycle release: “WordPress 7.1.5 is a short-cycle release. The next major release will be version 7.2, currently planned for December 8th.” The announcement says that sites which support automatic background updates will begin the update automatically. If you manage updates yourself, or you run a fleet of client sites, check this one today rather than batching it into your usual update window.

For the server-side changes in the ‘Mary Lou’ release that this one follows, see our earlier piece on what changes for your server, not just your editor.

The fixes that matter most to a hosting account

The notes for the WordPress 7.1.5 security release list each fix with the person who reported it. This section picks out the ones that touch the parts of a site a hosting account depends on. The entry to read first is worded by WordPress.org as “Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.” In general terms, unauthenticated means no login is needed to attempt it, and remote code execution means running code on the server.

Anyone who runs a multisite network should also read this entry: “A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.” Several other entries are worth knowing about:

  • “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 information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.”
  • “Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.”
  • “Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).”
  • “Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.”
  • “A reflected XSS in the legacy media library popup, reported by Anthropic.”

The remaining entries include more cross-site scripting (XSS) fixes, in the Interactivity API context helper, oEmbed provider responses, Customizer previews, the Comment Date block and the block editor. They also include an authorization bypass in comment editing, an Editor+ information disclosure through author assignment in the REST API, and an information disclosure through XML-RPC wp.getComments. Two are hardening changes: 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 is already gone.

What the release says about older branches

WordPress.org says that, as a courtesy, the security fixes were backported to all branches eligible to receive security fixes (currently through 4.7). It then adds: “The backports are in progress and will ship as they become ready.” It also reminds readers that only the most recent version of WordPress is actively supported. If you deliberately run an older major version, check whether the WordPress 7.1.5 security release fixes have appeared for your branch rather than assuming they already have. Because only the latest version is actively supported, moving to 7.1.5 is the more reliable option.

The same section notes a separate change: “In WordPress 7.0, 1024 bit certificates were removed from bundled root certificates. This change has been applied to 6.9.12 and earlier as part of this release.”

What to check after the WordPress 7.1.5 security release

Updating to 7.1.5 applies the fixes. A short check afterwards is still worth doing, because several of the fixes ran through surfaces that handle content from outside your team:

  • Confirm the version number in your dashboard reads 7.1.5 (or, on a test site, 7.2 RC 2 or later), since WordPress.org states “WordPress 7.2 RC 2 has also been released, containing all applicable fixes.” Automatic update emails can be missed or filtered.
  • Review recent Customizer changeset previews and content submitted through comments for injected script tags or shortcode attributes you did not write. Two of the entries above ran through those surfaces: the SQL injection via Customizer changeset previews and the stored XSS via shortcode attributes in comments. The multisite takeover entry also involves Customizer previews.
  • On a multisite network, review who holds the Administrator role on individual sites, since one fix covers a site Administrator taking over a Super Admin account.
  • If a proxy or caching layer in front of your site logs REST API requests, those logs may help you look back for unusual search or comment-endpoint requests. This is our suggestion, not something the announcement says.
  • If you do not rely on XML-RPC, consider disabling it. Some remote publishing tools and plugins still use it, so check before switching it off. The pingback denial-of-service entry and the wp.getComments disclosure both ran through it.
  • Plugin-level and object caches can keep serving a pre-patch response after core is updated, so clear them, not only your CDN cache. (General WordPress knowledge, not from the release notes.)

None of this requires special tooling. It is the same kind of log review you would do after any disclosed vulnerability in software your site depends on. These checks are a starting point, not a full security audit. Finding nothing does not prove a site was unaffected before it was updated, and if you see signs of compromise, get help from a security professional.

What the WordPress 7.1.5 security release announcement does not say

It is worth being direct about the gaps in the announcement. It does not assign CVE identifiers to any of the fixes listed. It also does not say whether any of these issues were exploited before the patch shipped, or how long each one existed before it was reported. If a CVE entry or a vendor confirmation of active exploitation appears later, treat it as new information rather than something this announcement already told you.

Where this leaves the WordPress 7.2 timeline

The same announcement confirms that “WordPress 7.2 RC 2 has also been released, containing all applicable fixes.” The announcement gives the 7.2 final release as “currently planned for December 8th,” which lines up with what we covered in WordPress 7.2’s Secrets API: What Your Host Needs to Test Before December 8. If you are staging a 7.2 test environment ahead of that date, use RC 2 or later so you are not testing a build that predates these fixes.

What to do now

Update to WordPress 7.1.5 today if you have not already, ideally after taking a current backup. The announcement says to download it from WordPress.org, or to open your dashboard, click “Updates”, then “Update Now”. If you manage several client sites, update all of them as soon as you can. The announcement does not rank the fixes by severity or limit them to particular setups. Then do the short check above on each site, paying extra attention to multisite networks and any site that still has XML-RPC enabled.

It is also a reasonable moment to confirm that automatic background updates are turned on for every site in your account, not just the ones you remember to check by hand. After this WordPress 7.1.5 security release, a quick note to clients saying the update happened and what it covered is worth sending even if they never asked.

Featured image: “Couple of metallic padlocks on old door frame” by Horia Varlan, licensed CC BY 2.0, via www.flickr.com.