Security Guides

WordPress 7.1.5 security release (18 November 2026): 20 fixes, including unauthenticated privilege escalation, multisite takeover and two SQL injections. What site owners should do today

WordPress 7.1.5 fixes 20 security issues, including unauthenticated privilege escalation and two SQL injections. How to update and check auto-updates.

Published 2026-11-19 Updated 2026-11-19 Last verified 2026-11-19 7 min read
On this page

For: anyone who runs a WordPress site (company site, blog, shop, multisite) and the IT staff, agencies or maintenance contractors who look after it. This article is based on the official WordPress.org announcement and does not cover attack steps.

Developing: this article will be updated as more is published

Who is affected

anyone who runs a WordPress site (company site, blog, shop, multisite) and the IT staff, agencies or maintenance contractors who look after it.

Confirmed so farSee the table ↓
  • Release
  • Number of fixes
  • Advice
Not yet confirmed
  • Per-version availability of backports to older branches (7.0, 6.9 and so on; the announcement says they ship as each is ready)
  • CVE numbers and severity for each item (not in the announcement)
  • Whether any item is exploited (the announcement does not say)
What to do nowSee the steps ↓
  1. Check your version
  2. Back up, then update
  3. Check auto-updates
3 more
  1. On an older branch, check your own branch
  2. Check plugins, themes and hosting
  3. Stop-gap steps until your branch is fixed (this site's advice)
Last checked
As of November 19, 2026 (JST)
Follow-up plans and what we checked

The official WordPress.org announcement (18 November 2026) says 7.1.5 is a short-cycle security release with 20 security fixes. It recommends updating immediately and says sites that support automatic background updates will begin updating automatically.

What to do today

1

Check your version

In the dashboard, go to Dashboard, then Updates, and read the current WordPress version. If it says 7.1.5, core is up to date. If not, go to the next step.

2

Back up, then update

Back up the site files and database, then choose Update Now. Afterwards, check the main functions: home page, login, comments, checkout. For how to think about backups, see Backup and recovery essentials.

3

Check auto-updates

The announcement says sites that support automatic background updates will begin updating automatically. If you turned them off (through a config setting, a maintenance plugin or hosting settings), update by hand. Why auto-updates fail to run depends on the environment.

4

On an older branch, check your own branch

The announcement says the fixes are being backported to all branches eligible for security fixes (currently through 4.7). Backports are in progress and ship as each is ready. If you run 7.0, 6.9 or another branch, check the Updates screen or WordPress.org for a new release of your branch and update when it appears. If it is not out yet, use the stop-gap steps below. The announcement also says only the most recent version is actively supported, so plan a move to the current line (this site's advice).

5

Check plugins, themes and hosting

Update plugins and themes separately from core, and delete the ones you do not use. Shared and managed WordPress hosts may update core for you, so confirm with the version shown. Ask anyone who handles updates for you when 7.1.5 (or your branch's latest) will be applied.

6

Stop-gap steps until your branch is fixed (this site's advice)

Review administrator and editor accounts and remove people who no longer need access. Reducing exposure also helps: turn off XML-RPC if you do not use it, and moderate comments. Details are in WordPress security. Also check for administrators you do not recognise and unexpected file changes (how to check for intrusion).

What was fixed (official list)

The WordPress.org announcement lists 20 items. They are grouped by type here. The conditions for each item (for example "Author+") follow the announcement's wording.

WordPress 7.1.5 security fixes (released 18 November 2026)
Privilege escalation
An unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. A multisite flaw that lets a site Administrator take over a Super Admin account through Customizer menu previews
SQL injection (2)
One through nested relation values in WP_Meta_Query. One through the front page setting in Customizer changeset previews
XSS (script injection)
Unauthenticated stored XSS through shortcode attributes in comments. Reflected XSS in the legacy media library popup. XSS through the store namespace in the Interactivity API. Contributor+: scripts in oEmbed provider responses, the date format of the Comment Date block, and media filenames when converting to a File block. Administrator stored XSS through Customizer previews. XSS in the block editor through Openverse image metadata
Denial of service
Unauthenticated denial of service through batched XML-RPC pingbacks
Information disclosure
Unauthenticated: private taxonomy terms exposed through the REST API search endpoint. Author+: user email addresses exposed through the REST API comments endpoint. Editor+: through post and template author assignment in the REST API. Subscriber+: through XML-RPC wp.getComments
Authorization bypass
Author+: through comment editing in the admin
Hardening
A malformed regular expression that broadened JSON media type matching was fixed. The block editor's Imgur embed variation was removed because its server-side provider is no longer available

This site's view: the heaviest items are those reachable without logging in (privilege escalation, stored XSS, denial of service, REST disclosure) and the multisite takeover. Sites that accept comments, and multisite networks that run many sites on one base, should update first. The announcement gives no attack details and this site does not add any.

Older branches and the certificate change

Backports and certificates (official announcement)
Backports
To all branches eligible for security fixes (currently through 4.7). In progress, shipping as each is ready
Support scope
The announcement says only the most recent WordPress version is actively supported
Certificates
WordPress 7.0 removed 1024-bit certificates from the bundled root certificates. As part of this release, the change was applied to 6.9.12 and earlier
Next major release
WordPress 7.2 is planned for 8 December. 7.2 RC 2 contains the applicable fixes

The certificate change concerns the list of root certificates WordPress uses when it connects to outside services over HTTPS. 1024-bit keys are considered weak today, so this removes them (this site's note). In rare cases a connection to an outside service that relied on an old certificate could be affected, so after updating, check features that call outside APIs, such as payments, notifications and feed fetching (this site's advice).

What is known and not known

ItemWhat was publishedStatus
Release7.1.5, 18 November 2026, short-cycle security releaseConfirmed (WordPress.org)
Number of fixes20, including unauthenticated privilege escalation, two SQL injections and stored XSSConfirmed (WordPress.org)
AdviceUpdate immediately; supporting sites update automaticallyConfirmed (WordPress.org)
Older branchesBackported to all eligible branches (currently through 4.7); in progressPer-version status not confirmed
CVE and severity per itemNot in the announcementNot confirmed
ExploitationNot mentioned in the announcementNot stated

If someone else runs your site

Ask your agency, maintenance contractor or host these three things.

  • Which WordPress version does the site run, and when will it move to 7.1.5 (or your branch's latest)?
  • Are auto-updates on, and is there a backup from before the update?
  • Have plugin and theme updates, and removal of unused ones, been done?

Timeline

  1. 28 October 2026

    WordPress 7.1.4 (security release) is released. See the WordPress 7.1.4 explainer.
  2. 18 November 2026

    WordPress 7.1.5 is released with 20 security fixes. Backports are in progress.
  3. 19 November 2026

    This site checks the official announcement and publishes this article.

Sources (official)

Checked on 19 November 2026.

  • WordPress.org, "WordPress 7.1.5 Release" (18 November 2026) — wordpress.org

Update history

2026-11-19: first version, based on the official WordPress.org announcement. CVE numbers and severity per item, and per-version availability of backports for older branches, could not be confirmed from the announcement.

Latest breaking reports

All breaking reports →

FAQ

QWhat happened?
A

The WordPress team released 7.1.5 on 18 November 2026, a short-cycle security release. The official announcement lists 20 security fixes and recommends updating immediately. Sites that support automatic background updates will begin updating automatically.

QWhich fix is the most serious?
A

From the official list: an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution; a multisite flaw that lets a site Administrator take over a Super Admin account through Customizer menu previews; two SQL injections; and unauthenticated stored XSS through shortcode attributes in comments. The announcement does not give CVSS scores.

QWhat should I do for my own site?
A

In the dashboard go to Dashboard, then Updates, and choose Update Now to WordPress 7.1.5. Take a backup first. If auto-updates are on, the update may already be done or will start soon. Confirm the version on the Updates screen.

QWhat about older branches such as 7.0 or 6.9?
A

The announcement says the security fixes are being backported to all branches eligible for security fixes (currently through 4.7). Backports are in progress and ship as each is ready. The announcement has no per-version table, so check the Updates screen or WordPress.org to see whether a new release for your branch is out. It also says only the most recent WordPress version is actively supported.

QDo plugins and hosting matter here?
A

These fixes are in WordPress core. Plugins and themes need their own updates. Shared and managed WordPress hosts sometimes update core for you. Confirm through the version shown in the dashboard or your provider's notices. If a provider or agency handles updates, ask when 7.1.5 (or the latest release of your branch) will be applied.

QIs it being exploited?
A

As of 19 November 2026, the WordPress announcement mentions no exploitation. This site could not confirm from the announcement any listing in CISA's Known Exploited Vulnerabilities catalog or any CVE numbers for the individual items. Check for updates, because the situation can change soon after release.