WordPress 7.1.5 Fixes 18 Security Holes, Including One That Needs No Login. How to Check Your Site Got It
WordPress 7.1.5 shipped on Nov. 18, 2026 with fixes for 18 vulnerabilities and two hardening changes, and the same fixes went out the same day to every older branch back to 4.7. Most sites update on their own, but not all. Here is what was fixed, what WordPress.org data says about who is still on old versions, and a script to check any site.
WordPress 7.1.5, a security release published on Nov. 18, 2026, lists 20 fixes: 18 vulnerabilities and 2 hardening changes, and WordPress.org asks every site owner to update immediately.
The most serious fix, per the release notes, is an unauthenticated privilege escalation through Template Part block attributes that "could lead to remote code execution."
The fixes were also released on Nov. 18 for every branch from 4.7 to 7.0, so a site on 7.0 needs 7.0.9, a site on 6.9 needs 6.9.12 and a site on 4.7 needs 4.7.40.
WordPress.org's own usage data, read on the evening of Nov. 19, 2026, shows 66.7% of reporting sites on the 7.1 branch, 33.3% on older branches, and about 0.9% on branches older than 4.7 that get no security fixes at all.
Of 30 well-known sites we checked on the evening of Nov. 19, 2026, 15 published their WordPress version, and 2 of those were still on versions WordPress.org marks insecure.
WordPress 7.1.5 is out, and it is a security release: published on Nov. 18, 2026, it fixes 18 vulnerabilities and adds 2 hardening changes, according to the release announcement. WordPress.org's advice is to update immediately. One of the fixes closes a hole that an attacker could use without logging in, which the release notes say "could lead to remote code execution."
Most WordPress sites install security releases on their own, so for many owners this is already done. The ones at risk are sites where automatic updates are switched off, blocked by a host or a version control setup, or stuck on a very old branch. Below: what was fixed, the right version number for every branch, what WordPress.org's own data shows about old versions, and a short script that checks any site. This applies to self-hosted WordPress sites in every country.
What does WordPress 7.1.5 fix?
The release notes list 20 entries, each credited to the person or team who reported it. Two are hardening changes rather than reported vulnerabilities (a tighter regular expression for JSON media types, and removing the block editor's Imgur embed, whose provider is already gone). The 18 vulnerabilities, grouped by who could use them:
No login needed: a privilege escalation through Template Part block attributes that "could lead to remote code execution"; stored cross-site scripting (XSS) through shortcode attributes in comments; disclosure of private taxonomy terms through the REST API search endpoint; and a denial of service through batched XML-RPC pingbacks.
Subscriber, contributor or author accounts: several stored XSS bugs (oEmbed responses, the Comment Date block, media filenames in the block editor), an authorization bypass when editing comments, and leaks of user email addresses and comments through the REST API and XML-RPC.
Editor and administrator accounts: XSS through Customizer previews, an information leak in the REST API, and on Multisite, a way for a site administrator to take over a Super Admin account.
Other (the notes don't say which account is needed): two SQL injection bugs (in WP_Meta_Query and in Customizer changeset previews), XSS in the Interactivity API context function, XSS in the block editor through Openverse image metadata, and reflected XSS in the legacy media library popup.
The announcement gives no severity scores. It also notes that 7.1.5 is a short-cycle release, and that WordPress 7.2 is planned for Dec. 8, 2026, with the same fixes already in its second release candidate. Two of the reports are credited to Anthropic, the AI company.
Which version should my site be on?
WordPress backported the fixes to every branch still eligible for security fixes, which the announcement says currently goes back to 4.7. All of them were released the same day. We read the release dates from WordPress.org's download server, and the version status from its version check API, which lists every release as latest, outdated or insecure:
If your site runs
It needs at least
Released (UTC)
7.1
7.1.5
Nov. 18, 16:35
7.0
7.0.9
Nov. 18, 16:37
6.9
6.9.12
Nov. 18, 16:39
6.8
6.8.13
Nov. 18, 16:42
6.7
6.7.12
Nov. 18, 16:45
6.6
6.6.12
Nov. 18, 16:48
6.0 to 6.5
6.0.19, 6.1.17, 6.2.16, 6.3.15, 6.4.15, 6.5.15
Nov. 18, 19:06 to 19:25
5.0 to 5.9
5.0.32 up to 5.9.21
Nov. 18, 19:28 to 20:05
4.7 to 4.9
4.7.40, 4.8.35, 4.9.36
Nov. 18, 20:09 to 20:21
4.6 or older
No fix. Move to a supported branch
Every earlier release in each branch, including 7.1.4 from Oct. 28, is now marked insecure by the API. The announcement adds that "only the most recent version of WordPress is actively supported," so an old branch with a fresh patch is safer than it was yesterday, not a long-term plan.
How many sites are still on old versions?
WordPress.org publishes the share of sites on each major branch, counted from the sites that check in with its update servers. We read the statistics API at 9:40 p.m. Eastern on Nov. 19, 2026 (02:40 UTC Nov. 20):
66.654% of reporting sites run the 7.1 branch.
33.274% run an older branch (7.0 is 6.198%, 6.9 is 6.024%, 6.8 is 4.801%).
7.223% run something older than 6.0.
0.946% run a branch older than 4.7 (3.0 to 4.6), which received no fix at all.
These figures are by branch only, so they can't tell a site on 7.1.5 from one on 7.1.2. That is what the next test is for.
We checked 30 sites: what they reveal
A WordPress site usually announces its version in two places: the <generator> line of its RSS feed (https://wordpress.org/?v=7.1.5) and a <meta name="generator"> tag in the page head. We wrote a script that reads either one and checks the result against the version check API, then ran it on 30 well-known sites that use WordPress (media companies, corporate newsrooms, WordPress hosts and plugin makers) the same evening, about 30 hours after the last backport shipped.
15 sites published no version. They hide it, which is common on managed hosts and security plugins, or their feed is not standard WordPress.
4 ran a 7.2 release candidate. Three are WordPress.org's own sites and the fourth is cofounder Matt Mullenweg's blog.
4 were already on 7.1.5.
5 were on a patched release of an older branch: four on 6.9.12 and one on 7.0.9. Those sites took the backport within hours, which is what a well-run managed platform looks like.
2 were on versions marked insecure: one on 7.1.2 and one on 6.3.14. We are not naming them; both are likely to update soon, and a published version can lag behind a cached feed.
The lesson for an owner: hiding the version number does not protect you, because automated attacks commonly try known exploits on every site they reach without checking the version first. Being on the fixed release does.
How do I check and update my own site?
Look at Dashboard, then Updates. The screen says which version you run and offers an "Update Now" button if a newer one exists. Back up first if your host doesn't do it for you.
Check that automatic updates are on. WordPress installs minor and security releases by itself by default, per the Upgrading WordPress documentation. Two lines in wp-config.php turn that off: define( 'AUTOMATIC_UPDATER_DISABLED', true ); stops all automatic updates, and define( 'WP_AUTO_UPDATE_CORE', false ); stops core updates. If you find either and don't know why it is there, ask whoever built the site. WP_AUTO_UPDATE_CORE set to 'minor' is fine: it still installs security releases.
Run the check from outside. The script below works on your own site, a client's or a competitor's, as long as the version is published. Hidden versions need step 1.
Treat the unauthenticated bugs as urgent if you can't update today. Sites that accept comments from the public and keep XML-RPC on are the ones the "no login needed" fixes protect most. If you can't update within a day, turning off XML-RPC (many security plugins have a switch) and closing comments for a day are reasonable stopgaps, not fixes.
Update your plugins too. A core release doesn't touch plugins, and plugins are where most WordPress compromises start; our Gootloader post shows what a hacked site gets used for.
The script
Save it as wp-version-check.mjs and run it with Node 18 or newer: node wp-version-check.mjs https://example.com. It is read-only: it fetches the feed and home page once and asks WordPress.org's public API for the status of the version it finds.
// wp-version-check.mjs: which WordPress version does a site report, and is it patched?// Usage: node wp-version-check.mjs https://example.com [https://another.com ...]// Reads the version a site publishes in its RSS feed or its generator meta tag,// then checks it against WordPress.org's own list of secure and insecure releases.const UA = 'Mozilla/5.0 (compatible; wp-version-check/1.0)';async function get(url) { try { const res = await fetch(url, { headers: { 'user-agent': UA }, redirect: 'follow', signal: AbortSignal.timeout(15000) }); return res.ok ? await res.text() : ''; } catch { return ''; }}function findVersion(text) { // RSS: <generator>https://wordpress.org/?v=7.1.5</generator> // HTML: <meta name="generator" content="WordPress 7.1.5" /> const m = text.match(/wordpress\.org\/\?v=(\d+\.\d+(?:\.\d+)?)/i) || text.match(/content=["']WordPress (\d+\.\d+(?:\.\d+)?)/i); return m ? m[1] : null;}const parts = (v) => v.split('.').map(Number);const newer = (a, b) => { const x = parts(a), y = parts(b); for (let i = 0; i < 3; i++) { if ((x[i] || 0) !== (y[i] || 0)) return (x[i] || 0) > (y[i] || 0); } return false; };const status = await (await fetch('https://api.wordpress.org/core/stable-check/1.0/')).json();// Newest release in each branch (7.1, 7.0, 6.9 ...): the version a site on that branch should run.const newestInBranch = {};for (const v of Object.keys(status)) { const branch = v.split('.').slice(0, 2).join('.'); if (!newestInBranch[branch] || newer(v, newestInBranch[branch])) newestInBranch[branch] = v;}for (const raw of process.argv.slice(2)) { const site = raw.replace(/\/+$/, ''); const version = findVersion(await get(`${site}/feed/`)) || findVersion(await get(site)); if (!version) { console.log(`${site}\tno version published (hidden, or not WordPress)`); continue; } const branch = version.split('.').slice(0, 2).join('.'); const fixed = newestInBranch[branch]; const latest = Object.entries(status).find(([, x]) => x === 'latest')[0]; const s = status[version] || (newer(version, latest) ? 'prerelease' : 'unknown'); const verdict = s === 'insecure' ? `INSECURE: update to ${fixed} or later` : s === 'latest' ? 'up to date' : s === 'outdated' ? `patched (security fixes for the ${branch} branch); newest release is ${latest}` : s === 'prerelease' ? `beta or release candidate, newer than ${latest}` : 'unknown version'; console.log(`${site}\t${version}\t${verdict}`);}
A line of output looks like this: https://example.com 6.9.12 patched (security fixes for the 6.9 branch); newest release is 7.1.5. Because the script reads the version list live, it stays correct after the next release without changes.
What we don't know yet
Whether any of the bugs are being exploited. The announcement doesn't say, and we found no report of attacks on these specific issues as of the evening of Nov. 19. The last big one is a warning, though: after WordPress 7.1.2 fixed CVE-2026-87902 on Sept. 22, 2026, Patchstack reported the first attack attempts on its firewall at 11:49 UTC the same day.
Technical details. WordPress.org lists each issue in one line. Security firms usually publish more once most sites have updated.
Exactly how many sites are on 7.1.5. WordPress.org's statistics stop at the branch, so the share of fully patched sites isn't public.
Our view: if your site updates itself, confirm it did and move on. If it doesn't, this is the release to fix that, because the next one will matter just as much. And if you're on a branch older than 4.7, no update is coming; plan the move to a current version this month, and test it on a staging copy first.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.