Skip to content

Update to WordPress 7.1.5 for 20 security fixes

WordPress 7.1.5, released 18 November 2026, fixes 20 security issues three weeks after 7.1.4. What it fixes and how to check your site has updated.

5 min readSouthWest WebPress team

WordPress 7.1.5 was released on 18 November 2026 as a security release, and WordPress recommends updating immediately. Every WordPress site is affected. It arrives three weeks after 7.1.4, so if you have only just updated to 7.1.4, you need to update again. Most sites should update automatically, but it is worth checking that yours has.

What 7.1.5 fixes

The official announcement lists 20 items. WordPress describes two of them as hardening, which means precautionary changes rather than fixes for a known weakness:

  • a regular expression (a text-matching pattern) that matched JSON media types too broadly
  • removal of the block editor’s Imgur embed option, because that provider no longer exists

The other 18 fix specific security problems. You may see slightly different totals quoted elsewhere. We have used WordPress’s own list.

Issues that need no login

These matter most, because anyone visiting your site could try them:

  • Privilege escalation through Template Part block attributes, which WordPress says “could lead to remote code execution”. That means an attacker could run their own code on your server. This looks like the most serious item in the release.
  • Stored cross-site scripting (XSS) through shortcode attributes in comments. XSS means malicious script injected into your pages, where it can run in visitors’ or administrators’ browsers.
  • Denial of service through batched XML-RPC pingbacks, which could knock a site offline.
  • Private taxonomy terms (such as categories and tags) exposed through the REST API search endpoint.

Issues that need a logged-in account

Several fixes cover problems that someone with an account could exploit. They range from the Subscriber role, the most basic account type, up to Administrator:

  • Subscriber and above: information disclosure through XML-RPC.
  • Contributor and above: three XSS issues, involving oEmbed responses, the Comment Date block, and media filenames when converting a media block to a File block.
  • Author and above: user email addresses exposed through the REST API comments endpoint, and an authorisation bypass when editing comments in the admin.
  • Editor and above: information disclosure through post and template author assignment in the REST API.
  • Administrator: stored XSS through Customizer previews. On multisite networks, a site Administrator could take over a Super Admin account through Customizer menu previews.

These are a lower risk if you are the only person who logs in. They matter more if people can register on your site, or if staff, freelancers or agencies have accounts.

Other fixes

The release also fixes two SQL injection issues, which means tampering with database queries. One is in WordPress’s meta query code and one involves the front page setting in Customizer previews. It also fixes three more XSS issues: in the legacy media library popup, in an Interactivity API function, and in the block editor through Openverse image metadata.

In total, 17 core files changed, covering comments, the Customizer, meta queries, oEmbed, XML-RPC, the REST API, shortcodes and the Interactivity API.

How it compares with 7.1.4

WordPress 7.1.4 was released on 28 October 2026. Its summary also describes fixes for multiple issues and recommends updating immediately. We covered it in our post on 7.1.4.

We have not been able to confirm how many issues 7.1.4 fixed, so we are not going to claim that 7.1.5 is bigger. For context, WordPress 7.1.1 on 17 September 2026 contained 11 security fixes.

The practical point is simple. Being on 7.1.4 does not protect you from the issues fixed in 7.1.5. A site that updated in late October is still exposed until it moves to 7.1.5.

Is anyone exploiting these issues?

None of the official sources we have read say that any of these issues are being exploited. No CVE numbers, severity scores or technical write-ups had been published in those sources at the time of writing.

That is not a reason to wait. Once fixes are public, attackers can compare the old and new code to work out what changed. Core releases are a common target for exactly that reason. The safest position is to be on 7.1.5 within days, not weeks.

Older versions of WordPress

WordPress has also produced fixes for older branches back to 4.7, including 7.0.9, 6.9.12, 6.8.13, 6.7.12 and 4.7.40.

  • Versions 7.0 and 6.5 to 6.9 are affected by all 20 issues.
  • Older branches are affected by fewer, down to 11 of the 20 for 4.7.
  • WordPress 4.6 and earlier no longer get security updates.
  • Only the latest version is actively supported.

The two official pages differ slightly on timing. One says the older-branch fixes will ship as they become ready, and the other says they have been released. If you run an older branch and do not see an update yet, check again shortly.

Versions 6.9.12 and earlier also drop 1024-bit certificates from the root certificates bundled with WordPress. This matches a change already made in WordPress 7.0.

The next major version, WordPress 7.2, is planned for 8 December 2026. If you are testing the 7.2 release candidate, RC 2 already includes these fixes.

What you should do

If we look after your website

You do not need to update anything yourself. If you would like confirmation that your site is on 7.1.5, or you have concerns about who has accounts on your site, get in touch.

If you manage it yourself

  1. Log in and go to Dashboard → Updates. If WordPress 7.1.5 is offered, take a backup and click “Update Now”.
  2. If no core update is offered, your site has most likely already updated itself through automatic background updates. Sites that support them start updating on their own. If you are unsure, ask your host to confirm the version.
  3. Do not assume 7.1.4 is enough. If you updated manually three weeks ago and have automatic updates switched off, you will need to update again.
  4. If you are on an older branch, update to 7.1.5 if you can. If you cannot, apply your branch’s security release as soon as it is available, and plan a proper upgrade. Only the latest version is actively supported.
  5. If you run a multisite network, treat this as a priority because of the Super Admin takeover fix.
  6. After updating, check the things that earn you money. Place a test order or send a test enquiry form.

It is also a good moment to review user accounts. Remove logins for people who no longer need them, and make sure nobody has a higher role than their work requires. Several of these fixes only matter if someone with an account decides to misuse it.

If keeping on top of releases like this is taking more of your time than you would like, our care plans cover core, plugin and theme updates, with checks afterwards.

Keep reading

All posts
Security5 min read

What to ask your host about the Apache HTTP/2 flaw

A critical flaw in Apache’s HTTP/2 module sits below WordPress, so plugin updates won’t fix it. Here is how to check your server and what to ask your host.

Let’s talk about your website

Book a call with our team. We will talk through your business, your goals and how your website can do more for you – then recommend a clear next step.