WordPress 7.1.5: update your client sites

WordPress released 7.1.5 on 18 November and recommends updating immediately. For an agency looking after client sites, the task is to get the patch onto each installation and check the parts clients depend on. If those updates keep falling to the developer who happens to be available, use this release to review who should operate the hosting.

Author
Intercube
Published
Reading time
4 min read

01

Start with the client sites you actually run

An agency portfolio can include separate WordPress installations and several sites sharing one multisite network. Record the installed core version for each installation and check the result of any background update. A network contains several client sites, so its update needs checks across the network.

Include websites that rarely change. A quiet brochure site can still collect enquiries, and the person whose inbox receives them may be the first to notice a broken form. Agree a short check with each client or account owner before treating the update as complete.

02

What changed in 7.1.5

The release announcement lists fixes affecting access control and user content, including a multisite issue in which a site administrator could gain Super Admin access. It also describes a privilege escalation through Template Part block attributes that could allow code execution without a logged-in account.

Sites on the 7.1 branch should move to 7.1.5. If a client runs an older branch, verify that the corresponding security release is available and installed. The project is publishing backports as they become ready. Use stable releases for production and a separate environment for testing WordPress 7.2.

03

Check the action that matters to the client

After the core update, send a test enquiry and confirm receipt at the intended destination. For a shop, place a test order and follow it through payment and fulfilment. In multisite, check the relevant sites and the roles used to manage them. Save the outcome with the version that was installed.

If you find an unexpected administrator, changed files or unfamiliar scheduled work, preserve the evidence and investigate the installation. Agree who handles the investigation and whether recovery from a known clean copy is needed before returning the site to normal operation.

04

Move repeated hosting work to Intercube

Intercube can prepare a staging environment and coordinate the infrastructure side with your WordPress maintainer. Your developer can check themes, plugins and client workflows while our engineers handle the environment and the agreed runtime and service configuration. That gives the agency someone to work with when the update exposes an infrastructure problem.

For code managed in a repository, deployment pipelines are included in the managed hosting plan. Your team can release through Intercube without a separate GitHub Actions deployment setup or runner bill for that pipeline. If you want to move client sites, migration to Intercube managed hosting is included at no additional cost.

Before you close the update

  • Confirm the installed security version for each installation.
  • Check every relevant site in a multisite network.
  • Test an enquiry or order through to its destination.
  • Investigate unexpected access or changed files.
  • Record who handles the next hosting or update problem.

Sources

Move your client sites to Intercube

Tell us which sites you maintain and how updates happen today. We can plan the hosting move with your team.

Discuss your client hosting