Skepra / Web recovery & resilience

WordPress 7.1.5 Release

A WordPress security update changes the risk decision but the owner does not know which exposed paths to retest.

Discuss the next maintenance decision

WordPress 7.1.5 was published on November 18, 2026 as a security release. The official notice lists fixes across multisite permissions, REST API information disclosure, XML-RPC denial of service, XSS, SQL injection and block-editor behavior. It recommends updating immediately and says the fixes are being backported to supported branches through 4.7. These facts do not prove that a particular site is affected. They define a decision: identify the site version and exposed feature paths, then choose an update and verification route.

Start with the site and package boundary

Record the exact WordPress core version, whether the site is single-site or multisite, the PHP runtime, update channel and the owner of the deployment. Do not treat a dashboard message on one site as evidence for every client site. A managed fleet may contain different branches, frozen staging copies or source-controlled WordPress files.

The release contains several conditions. A multisite owner should review administrator and Super Admin boundaries. A site that exposes REST search or comments endpoints should confirm which authentication and data-visibility rules are intended. A site that accepts XML-RPC should record whether pingbacks are needed. A block-heavy site should include editor, media and template-part workflows in its test plan.

Build a feature-path matrix

Use a small worksheet with one row per relevant path:

  • core version and corrected target;
  • single-site or multisite mode;
  • REST endpoints used by the frontend, plugins or integrations;
  • XML-RPC enabled state and business reason;
  • media, comments, embeds and block-editor flows;
  • test URL or synthetic request;
  • expected result, observed result and owner.

The worksheet prevents a generic update from being mistaken for a completed review. For example, a successful homepage request does not validate a multisite Customizer preview or a REST endpoint used by a client dashboard.

Update in a reversible order

Use a clean staging copy and keep a recovery reference before changing the production site. Apply the vendor-supported WordPress update through the authorized deployment path. Confirm the exact version from the running site or artifact after the update, not only from the command that started it.

Run synthetic checks for login, editorial save, media upload, comments, REST integrations, XML-RPC if retained, and the client journey that matters most. For multisite, test a site Administrator and a Super Admin separately. Keep test identities and data separate from customer records.

If a test fails, record the failing path and the responsible plugin, theme, proxy or deployment unit. Do not disable security controls broadly to make the check pass. The next decision may be a bounded compatibility fix, a controlled rollback while the update remains scheduled, or a handoff to the hosting or plugin owner.

Applicability and handoff

This article applies conditionally to WordPress installations covered by the 7.1.5 notice or its backports. It does not assert exploitation, affected customers or a universal need to change XML-RPC, REST or multisite settings. Its practical output is a version-and-feature-path acceptance record that an owner, agency or MSP can review before closing maintenance.

Primary source: WordPress 7.1.5 Release.