← All articles

WordPress 7.1.5 Security Update: 18 Fixes You Should Install Now

By VonixCo Team · · 13 min read

A laptop showing the WordPress 7.1.5 security update screen with a shield icon on a clean office desk

WordPress 7.1.5 is a security release, published on November 18, 2026, that fixes 20 issues in WordPress core — 18 vulnerabilities and two hardening changes — and WordPress recommends updating immediately. The most serious flaw is an unauthenticated privilege escalation through Template Part block attributes that, in WordPress’s own words, “could lead to remote code execution” — an attacker running code on your server. The release also fixes two SQL injection flaws, several cross-site scripting (XSS) flaws, information disclosure, and a denial-of-service flaw. Update now — this article explains what changed, who is affected, and how to update safely.

This article is based on the official WordPress 7.1.5 release post, read in full, and on Roger Montti’s November 19 coverage in Search Engine Journal, with severity counts cross-checked against Wordfence’s analysis. Where the sources count the flaws differently, that difference is stated rather than smoothed over.

What is WordPress 7.1.5?

WordPress 7.1.5 is a short-cycle security release. Short-cycle means it exists for one purpose: to ship security fixes quickly, without waiting for the next major release. The official announcement is direct: “Because this is a security release, it is recommended that you update your sites immediately.” Update from your WordPress dashboard under Updates, or download 7.1.5 from WordPress.org. Sites with automatic background updates should receive it automatically — but check that it actually arrived.

The release lists 20 fixes. Eighteen are vulnerabilities and two are hardening changes — improvements that make an attack harder even though they do not fix a specific exploitable flaw. Four of the flaws are labelled “unauthenticated” in the official post, meaning no login is needed to trigger them. Wordfence, which tracks each flaw individually, counts 19 distinct vulnerabilities — one bullet covers two flaws — and eight that need no login. The difference is a matter of counting: the fix list and the advice are the same either way.

WordPress 7.1.5 is not the end of the line. The next major release, WordPress 7.2, is planned for December 8, 2026, and WordPress 7.2 RC 2 already contains all of these fixes. The 7.1.5 fixes were also backported to all branches still eligible for security fixes, currently through version 4.7. The official reminder still stands: only the most recent version of WordPress is actively supported.

What is the worst flaw in WordPress 7.1.5?

The worst flaw is an unauthenticated privilege escalation via Template Part block attributes, reported by Logan Homolka. WordPress describes it as a privilege escalation “that could lead to remote code execution”. Search Engine Journal calls that combination “the worst-case scenario for a CMS”, and it is easy to see why. Remote code execution means an attacker can run their own code on your server from somewhere else over the internet. From there, as Search Engine Journal explains, they can read or change files, write to the database, create admin accounts, install backdoors, or inject malware.

A Template Part block inserts a piece of a template — such as a header or footer — into a page on a block theme, and the flaw is in the block’s theme and slug attributes. According to Cloudflare’s analysis of the patched code, an unauthenticated attacker can send an administrator a crafted editor link. When the administrator opens that link while signed in, the request can create an administrator account for the attacker, who can then run code by uploading a plugin.

Two points keep this in proportion. First, the flaw needs no attacker account — that is what “unauthenticated” means here — but the attack chain needs an administrator to open a crafted link while signed in. It is not a flaw an attacker can fire at a site and take over with no human involvement. Second, it is fixed. The patch is already out, and installing it removes the risk. The danger is leaving a site unpatched after the fix has been published and the details are public.

What else does WordPress 7.1.5 fix?

The remaining fixes fall into four groups. Cross-site scripting, or XSS, is the largest: eight of the fixes address it. The most exposed is an unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad of Awesome Motive. A visitor can post a comment whose shortcode attribute turns into script after it is saved, and that script then runs in the browser of anyone who views the comment — including an administrator, which can lead to account takeover. It needs a Comments or Latest Comments block in post content to bite. The other XSS fixes need an account of some level: Contributor-level XSS through oEmbed responses, the Comment Date block, and media filenames; XSS via Openverse image metadata and Customizer previews; and a reflected XSS in the legacy media library popup, reported by Anthropic.

Two SQL injection flaws are fixed. One is in WP_Meta_Query, through nested relation values in the code WordPress uses to build database queries involving metadata, reported by Christiaan Swiers. It is reachable through a plugin or theme that passes untrusted nested input into a meta query. The other is in Customizer changeset previews, through the front page setting, reported by Rudy Faile of the WordPress Security Team.

Four information disclosure flaws are fixed. Private taxonomy terms — the labels WordPress uses to sort content, such as navigation menus — were exposed through the REST API search endpoint; that one was reported by Anthropic. User email addresses were exposed through the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team. Post and template author assignment was exposed through the REST API, and comment data was exposed through the XML-RPC wp.getComments method.

The remaining fixes are a denial-of-service flaw and two privilege problems. The denial of service is an unauthenticated flaw in batched XML-RPC pingbacks, reported by Giovanni Cintolo, which could be used to knock a site offline. On multisite networks, a site administrator could take over the network’s Super Admin account through Customizer menu previews, reported by Yuval Miller. An authorization bypass in admin comment editing, reported by Jesse McNeil, let Author-level users edit comments beyond their permissions; Wordfence notes this bullet covers two distinct flaws. The two hardening changes are a corrected regular expression for JSON media type matching and the removal of the block editor’s Imgur embed variation, whose server-side provider no longer exists.

Vulnerability type Who it affects Login needed?
Privilege escalation via Template Part block (could lead to remote code execution) Any WordPress site No — but an administrator must open a crafted link
Stored XSS via shortcode attributes in comments Sites with a Comments or Latest Comments block No
Denial of service via batched XML-RPC pingbacks Any site with XML-RPC enabled No
Information disclosure via REST API search Any site No
SQL injection in WP_Meta_Query Sites whose plugins or themes pass untrusted input Depends on the plugin or theme
Multisite privilege escalation to Super Admin Multisite networks Yes — a site Administrator account
Stored XSS in the block editor and Customizer Sites with Contributor-level users or above Yes — Contributor to Administrator

Hands typing on a laptop keyboard while a website security update runs on the screen

Who is affected by the WordPress 7.1.5 flaws?

Any site running WordPress 7.1 before 7.1.5 is affected, and the same fixes were shipped for older branches on the same day. Fixed versions for the recent branches are 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12 and 6.5.15, with further releases for branches back to 4.7. If your site is on an older branch, install the patched release for that branch — or, better, plan an upgrade, since only the newest version is actively supported.

The practical question is not which branch you are on but whether the patch has actually landed. Sites with automatic background updates should have received 7.1.5 on their own, but automatic updates can fail silently — a host restriction, a file-permission problem, or a plugin conflict can stop them. Open Dashboard, then Updates, and read the version number yourself. If it does not say 7.1.5, or the patched version for your branch, update manually.

Has anyone exploited the WordPress 7.1.5 flaws?

As of November 20, 2026, no CVE identifiers had been published for these flaws, and no exploitation had been reported. Cloudflare’s briefing, reviewed on November 19, states that no source it reviewed reported exploitation in the wild, and that the CISA Known Exploited Vulnerabilities catalog had no entry for them. That is good news — but it is a snapshot, not a guarantee.

The reason to update quickly anyway is that the release notes are public and the patches are public. Security researchers and attackers alike can compare the patched code with the unpatched code and work out exactly what was wrong. That is normal for open-source software, and it is why WordPress says to update immediately rather than at your convenience. The previous release is a useful reminder: WordPress 7.1.4 fixed a flaw in the update process itself, CVE-2026-119977, which CISA lists as exploited.

How do you update to WordPress 7.1.5 safely?

A security update is urgent, but it is still an update. Ten minutes of preparation avoids the two classic mistakes: updating without a backup, and updating during your busiest hour. Work through these steps in order.

  1. Back up first. Take a full backup — files and database — and confirm you can actually restore from it. If your host takes automatic backups, check that a recent one exists first.
  2. Pick a quiet moment, or use staging. Update during off-peak hours for your audience. If your host offers a staging copy, run the update there first and click through the site before pushing it live. For a small site without staging, off-peak hours are enough.
  3. Update WordPress core. In your dashboard, go to Dashboard, then Updates, and click “Update Now”. If your site supports automatic background updates, check the version number afterwards to confirm the update actually ran.
  4. Update plugins and themes next. Update plugins and your theme after core, not before — plugin updates often include their own security fixes. Update them one at a time on an important site so you can tell which one caused a problem if something breaks.
  5. Verify the site works. Open the homepage and a few key pages as a visitor, not just in the admin. Test the contact form, the search box, and anything that takes money. If something looks wrong, restore the backup and work out which update caused it.
  6. Confirm the version. Go back to Dashboard, then Updates, and confirm the version reads 7.1.5, or the patched version for your branch. If you manage several sites, update them all — an unpatched site on the same hosting account is a way in.

A desktop monitor showing a website backup and maintenance checklist with an external hard drive beside it

What should you check after updating to WordPress 7.1.5?

Three checks are worth doing in the days after the update. First, watch Search Console. Open Indexing, then Sitemaps, and confirm the sitemap status reads “Success”. One small warning: if you open your sitemap in Chrome and see raw, unstyled XML, that is not a broken sitemap. Chrome 158 dropped support for client-side XSLT, which WordPress sitemaps used for styling, so the sitemap now displays as plain XML in that browser while crawlers read it exactly as before. Search Console is the source of truth, not the browser view.

Second, check that your pages are still being found. An update does not fix indexing problems — if pages were already struggling to get indexed, they will still be struggling after the update, and the fix for that is separate work. Our guide to fixing pages that are crawled but currently not indexed walks through the checks that matter. Third, do not read too much into traffic changes in the same week. The Google November 2026 core update is still rolling out, and our guide to the November 2026 core update for link builders explains why traffic should be judged only after the rollout finishes and a full week has passed.

Why does site security matter for link building?

Link building only pays off if the site receiving the links is healthy. A link pointing to a hacked, defaced, or blacklisted site loses its value, and a compromised site can lose the rankings those links were meant to support. Security is part of technical health, not a separate chore: the same discipline that keeps WordPress updated — checking the version, testing after changes, watching Search Console — is what keeps a site’s pages crawlable and indexable. Our guide to technical SEO for AI search covers the same point from the other side: search engines and AI systems can only recommend pages they can reach, trust, and read.

There is also a simpler reason. Guest posts are placed on other people’s sites, and those site owners check the site they are linking to. A site running a known-vulnerable WordPress version is a harder sell in outreach than a site that is clearly maintained.

When should you hire a service like VonixCo?

Updating WordPress is a job most site owners can do themselves in under half an hour. Hiring a service makes sense for the work around it: keeping a site’s content, links, and technical health moving every week, not just on the day a security release lands.

VonixCo is a niche-relevant guest posting and SaaS link building service based in Lahore, Pakistan. Its services are SaaS guest posts, niche guest posts, link building and guest post content writing, and its plans are $500 / $950 / $1,800 per month with content included and a live link report. Contact is info@vonixco.com and WhatsApp +92 340 0096621. A service like VonixCo fits when you want link building handled as an ongoing operation — prospecting, content, and outreach together — and when you need links from sites in your niche specifically. Before hiring anyone, ask how they vet sites and whether they report live links or just emails sent.

Frequently asked questions about WordPress 7.1.5

What is WordPress 7.1.5?

WordPress 7.1.5 is a security release published on November 18, 2026. It fixes 20 issues in WordPress core — 18 vulnerabilities and two hardening changes — and WordPress recommends updating immediately.

Is WordPress 7.1.5 a security update I need to install?

Yes. WordPress describes it as a security release and recommends updating immediately. The most serious flaw needs no attacker login and could lead to remote code execution, so delaying the update leaves a known, publicly documented hole open.

What is the most serious vulnerability fixed in WordPress 7.1.5?

An unauthenticated privilege escalation via Template Part block attributes, reported by Logan Homolka. It could lead to remote code execution, which would let an attacker run code on the server. The attack needs an administrator to open a crafted editor link while signed in, so it is serious but not automatic.

Do I need to update if my site is on an older WordPress version?

Yes. The fixes were backported to all branches eligible for security fixes, currently through version 4.7, so install the patched release for your branch. Only the newest version is actively supported, so plan an upgrade to a supported version as well.

Has anyone exploited the WordPress 7.1.5 vulnerabilities?

As of November 20, 2026, no exploitation had been reported and no CVE identifiers had been published for these flaws. That is good news, but the patches are public, so attackers can study them — update promptly rather than relying on the absence of reported attacks.

What should I do after updating to WordPress 7.1.5?

Confirm the version number in Dashboard, then Updates, check the homepage and key pages as a visitor, test forms and checkout, and update plugins and themes. Then check Search Console to confirm your sitemap status reads “Success” and your pages are still being indexed.

Conclusion

WordPress 7.1.5 is a straightforward security release with a clear instruction: update immediately. The headline flaw is serious — an unauthenticated privilege escalation that could lead to remote code execution — and the rest of the list covers XSS, SQL injection, information disclosure, and denial of service. Back up, update core, update plugins and themes, and verify the site. Then check that your pages are still indexed, and carry on building links to a site that is actually secure.

Want niche-relevant guest post placements?

Tell VonixCo about your website and niche, and we will reply with suitable publishing options and pricing.

Keep reading