WordPress maintenance Hacked site cleanup Security plugin Pricing Security tips
Home / Security tips / Website security
November 19, 2026

WordPress 7.1.5: Update Promptly to Fix Security Flaws

Your dashboard still says WordPress 7.1.4, but there’s another security release waiting. Should you stop taking orders? Assume someone has broken in? Neither follows from the version number alone.

You should, however, make time for WordPress 7.1.5 promptly. This is a security update, not a new-feature preview, and the job isn’t finished until you’ve confirmed what actually installed and checked that the site still works.

What WordPress 7.1.5 fixes

WordPress.org announced WordPress 7.1.5 on 18 November 2026 and recommends updating immediately. Eligible sites using automatic background updates may receive it without a manual installation.

The announcement describes a Template Part block privilege-escalation issue that can lead to remote code execution, plus fixes for comment script injection, multisite privilege escalation and information disclosure. Backports to eligible older branches through WordPress 4.7 are in progress. That doesn’t mean every older branch already has a patch; only the newest branch is actively supported.

Don’t wait for WordPress 7.2 or install a release candidate to deal with this. Use the stable security release. Also, the official announcement does not establish that these vulnerabilities are being actively exploited.


The serious risk has specific conditions

Patchstack’s original analysis, also dated 18 November, explains a distinction that can disappear in alarming headlines: an unauthenticated attacker doesn’t need an account, but the described route still requires an editor user to open crafted content.

Requests can then use the logged-in user’s authority. Whether that reaches code execution depends on sufficient privileges. This is not a claim that every subscriber can install plugins, or that reading any ordinary public page automatically compromises a site.

Serious? Yes. A reason to assume every visitor is infecting your shop? No.

A quick review of editor and administrator accounts is sensible, especially if former contractors still have access. Remove access they no longer need. But a tidy user list doesn’t replace the core update.

This release also addresses additional issues beyond the earlier upgrade-window problem discussed in our WordPress 7.1.4 security release guide. Reports about that older problem aren’t evidence of exploitation against these newly fixed issues.


Prepare a recovery route, not a week-long project

Before clicking Update, establish what you’re updating. Your public shop might be current while an old campaign site or a forgotten installation on a subdomain is still behind.

  1. Identify every WordPress installation you manage, including staging and older sites that remain accessible.
  2. Check that you have a recent database and files backup, and know how to restore it. A green backup notification alone isn’t proof of a usable recovery route.
  3. Confirm you can reach your hosting control panel or whoever handles recovery if WordPress admin stops loading.
  4. If staging is available, run a short compatibility check there. Don’t let an unfinished testing project postpone the security update indefinitely.

For a WooCommerce shop taking regular orders, think about backup timing too. Restoring yesterday’s database could remove today’s order records. Agree on a recovery approach before you need it rather than discovering that trade-off during an outage.

If someone else handles WordPress maintenance, give them a clear request: update promptly, verify the installed version and report the checks completed. “Updates are automatic” isn’t that report.


Install it, then verify the version

Use the official Dashboard > Updates screen. Follow the update prompts, let the process finish, then reload the screen and check that the installed version reads 7.1.5.

Don’t stop at the email saying an update was available. That’s an invitation, not confirmation.

The same applies to automatic background updates. They may already have done the work, but check the actual version. For a managed site, ask your provider to confirm the version and completion time for your specific installation, not just describe its general update policy.

If you’re on an older branch, ask which patched version is available for that branch and what the supported upgrade route is. Don’t read “backports in progress” as “everything old is covered.”


Check the parts customers actually use

A homepage loading successfully is a start. It’s a rather small start if your business depends on enquiries or payments.

  • Open key public pages, including a product or service page and the contact page.
  • Sign into admin, open the editor and check that ordinary editing still works without changing a live page unnecessarily.
  • Submit a clearly labelled test enquiry. Confirm it reaches an inbox you control, rather than trusting the form’s success message.
  • For WooCommerce, check product options, cart and checkout. Use a payment test method appropriate to your provider and setup; don’t casually run live charges.

Keep the checks proportionate. A specialist parts shop with delivery restrictions should test those restrictions; a training business should check its booking form. Your site’s money-making path deserves more attention than an unused sidebar.


If something fails, investigate before retrying

Read the error message and save it. Note the time, the version displayed and whether the public site or only admin is affected. Then consult the recovery guidance or ask your host or developer for help.

Repeatedly clicking Update isn’t a recovery plan. Neither is leaving a vulnerable version running for days after a rollback.

Our guide to what to do when a WordPress update breaks your site covers the compatibility side. If a rollback becomes necessary, treat it as temporary recovery with a named person responsible for completing the security update.


Updating and cleaning up are different jobs

Unexpected administrators, altered files or suspicious redirects need investigation. Preserve available logs and get qualified help with containment and hacked site cleanup. Installing a patch closes the addressed flaws; it doesn’t undo malicious changes that may already exist.

Don’t rotate every credential just because an update appeared. Let evidence guide incident-response decisions. And don’t treat a firewall or a clean plugin-scanner result as a substitute for updating WordPress core.

Assign one person to confirm three things today: the installed version, the completion time and whether the business-critical checks passed. That’s a much more useful answer than “I think it updated.”