Security notice
Run a site on WordPress? Version 7.1.5 is a security release with 20 fixes, including an unauthenticated flaw WordPress says can lead to remote code execution. Update today.
On November 18, 2026, WordPress released version 7.1.5, a security release. The official release post, by Jeremy Felt, lists 20 security updates and tells site owners to update immediately. One of those issues is an unauthenticated privilege-escalation flaw in Template Part block attributes that WordPress says can lead to remote code execution. Patchstack, in an article the same day, says that issue starts with an unauthenticated visitor and can end in remote code execution once an editor opens the content. The release post also lists an SQL injection issue in WP_Meta_Query through nested relation values. Patchstack says that issue can be reached without logging in, through a caller that passes request data into meta_query. The release post also lists unauthenticated stored cross-site scripting through shortcode attributes in comments. Patchstack says that issue also depends on a page with a Latest Comments block. Other fixes in the same release include further SQL injection, cross-site scripting and information-disclosure issues, a multisite privilege-escalation issue, an unauthenticated denial of service through batched XML-RPC pingbacks, and two hardening changes. Patchstack says it added 18 of the 20 items to its vulnerability database and treated the other two as hardening changes with no exploitable path, and that no CVE identifiers had been assigned at the time of publication. WordPress said the security fixes were backported to all branches still eligible to receive security fixes, currently through 4.7, and that the backports are in progress and will ship as they become ready. Patchstack says every branch back to 4.7 has a patched release, and that branches 4.6 and earlier no longer receive security updates. If your site uses automatic background updates, WordPress said the update process will begin automatically. Otherwise, update from the Dashboard under Updates, or download the release from WordPress.org. The WordPress release post and the Patchstack article do not report in-the-wild exploitation. As of November 19, 2026, we found no report of attacks using these flaws. If you run WordPress, update to 7.1.5, or to the fixed release for your branch, today. EverThread does not test for this. (WordPress 7.1.5 release, Nov 18; Patchstack, Nov 18)
What happened
- The release. WordPress 7.1.5 was released on November 18, 2026. The official release post calls it a security release, lists 20 security updates, and recommends that you update your sites immediately. You can install it from the WordPress Dashboard under Updates, or download it from WordPress.org. If your sites support automatic background updates, WordPress said the update process will begin automatically. (WordPress 7.1.5 release, Nov 18)
- The Template Part issue. The release post lists "Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution," reported by Logan Homolka. Patchstack describes the same issue as privilege escalation via Template Part block attributes that can lead to remote code execution, with no login required, once an editor user opens the content. The "can lead to remote code execution" wording is from WordPress. The condition that an editor opens the content is from Patchstack. (WordPress 7.1.5 release; Patchstack)
- The WP_Meta_Query issue. The release post lists "SQL injection in WP_Meta_Query via nested relation values," reported by Christiaan Swiers. It does not say whether that issue can be reached without logging in. Patchstack says the requirements are "Nothing (Unauthenticated), via a caller that passes request data into meta_query." That unauthenticated-caller detail is Patchstack's. (WordPress 7.1.5 release; Patchstack)
- The comments issue. The release post lists "Unauthenticated stored XSS via shortcode attributes in comments," reported by Rafie Muhammad of Awesome Motive, Inc. Patchstack says the same issue also depends on a page with a Latest Comments block. (WordPress 7.1.5 release; Patchstack)
- The rest of the release. The same 20 updates also include other SQL injection, cross-site scripting and information-disclosure issues, a multisite privilege-escalation issue that can let a site Administrator take over a Super Admin account through Customizer menu previews, an unauthenticated denial of service through batched XML-RPC pingbacks, and two hardening changes (a corrected regular expression for JSON media type matching, and removal of the block editor's Imgur embed variation). The full list is in the official release post. Patchstack says 18 of the 20 items are vulnerabilities and two are hardening changes with no exploitable path. (WordPress 7.1.5 release; Patchstack)
- No CVE identifiers yet. The official release post does not assign CVE identifiers. Patchstack says no CVE identifiers had been assigned at the time its article was published on November 18, 2026. (Patchstack, Nov 18)
- Backports. WordPress said the security fixes were backported to all branches eligible to receive security fixes, currently through 4.7, as a courtesy, and reminded readers that only the most recent version of WordPress is actively supported. It also said the backports are in progress and will ship as they become ready. Patchstack says every branch back to 4.7 has a patched release, and that branches 4.6 and earlier no longer receive security updates. If you are not on 7.1.x, install the fixed release for your branch when it is available, or confirm that it has already been published. (WordPress 7.1.5 release; Patchstack)
- No in-the-wild exploitation reported. The WordPress release post and the Patchstack article do not report attacks on live sites. As of November 19, 2026, we found no report of in-the-wild exploitation of the issues fixed in 7.1.5. Because no CVE identifiers have been assigned, there is nothing to list in CISA's Known Exploited Vulnerabilities Catalog. (WordPress 7.1.5 release; Patchstack)
Who should worry
Any website running a WordPress version before 7.1.5, including older branches that still receive security updates, through 4.7. Sites that already received 7.1.5, or the matching fixed release for their branch, through automatic updates are in a better position, but you should still confirm the installed version. If you do not run WordPress, this notice does not apply to you.
What to do now
- Update to WordPress 7.1.5, or to the fixed release for your branch, today. Back up the site first. In the Dashboard, open Updates and install the security release, or download it from WordPress.org. If automatic background updates are on, confirm that the site has moved to the fixed release. After the update, confirm the installed version. (WordPress 7.1.5 release)
- If you are on an older branch, install that branch's fixed release. WordPress said fixes were backported through 4.7 and that those backports are in progress and will ship as they become ready. Patchstack says every branch back to 4.7 already has a patched release. If you are on 4.6 or earlier, Patchstack says those branches no longer receive security updates; plan to move to a supported release. (WordPress 7.1.5 release; Patchstack)
- Confirm the site is on the new version. Check the version in the Dashboard after the update. If the update failed, try again from a backup, or have your developer, agency or host complete it.
If you run an online store or a membership site. These are general steps, not from WordPress or Patchstack. We are not claiming any tool, including EverThread, would have stopped an attack that used these flaws.
- Keep WordPress core on a release that still receives security updates, and do not ignore security releases.
- Review who has Contributor or higher access, and who is a site Administrator if you run multisite. Patchstack notes that several of the fixes concern what those roles can reach.
What to send your developer, agency or host
WordPress released 7.1.5 on November 18, 2026, as a security release with 20 security updates. The official release post includes an unauthenticated privilege-escalation issue in Template Part block attributes that WordPress says can lead to remote code execution. Patchstack says no CVE identifiers had been assigned at the time of its article, and that 18 of the 20 items are vulnerabilities. WordPress said the fixes were backported to all branches still eligible for security updates, currently through 4.7. The release post and the Patchstack article do not report in-the-wild exploitation. Please update us to WordPress 7.1.5, or to the fixed release for our branch, today, and confirm the installed version. Sources: WordPress 7.1.5 release, November 18, 2026; Patchstack, November 18, 2026.
Common questions
Does this mean my site was hacked?
No. A missing update is a reason to install 7.1.5, or the fixed release for your branch, and confirm the version. It is not proof of a break-in. The WordPress release post and the Patchstack article do not report in-the-wild exploitation.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see whether your site runs WordPress, which version it is on, or whether these flaws are present. A scan without a warning about this software does not mean your site is safe.
Which version should I install?
If you are on the 7.1 branch, install 7.1.5. If you are on an older branch that still receives security updates, install the fixed release for that branch. WordPress said those backports go through 4.7 and will ship as they become ready. Patchstack says every branch back to 4.7 has a patched release.
Are there CVE identifiers?
Not yet, as of the sources we checked on November 19, 2026. The official WordPress release post does not assign CVE identifiers. Patchstack said no CVE identifiers had been assigned at the time its November 18 article was published.
Is this being exploited?
The WordPress release post and the Patchstack article do not report exploitation on live sites. As of November 19, 2026, we found no report of in-the-wild exploitation of the issues fixed in 7.1.5.
Will automatic updates take care of this?
Possibly. WordPress said that if your sites support automatic background updates, the update process will begin automatically. You should still confirm that the installed version is 7.1.5 or the matching fixed release for your branch.
Where can I follow updates?
Follow the WordPress 7.1.5 release post, the WordPress 7.1.5 version documentation and the Patchstack article.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- WordPress 7.1.5 Release, November 18, 2026: official WordPress.org news post by Jeremy Felt. Calls 7.1.5 a security release, lists 20 security updates, and recommends updating immediately. Includes the unauthenticated Template Part privilege-escalation issue that "could lead to remote code execution," the WP_Meta_Query SQL injection, the unauthenticated stored XSS via shortcode attributes in comments, the other listed issues, and two hardening changes. Says the security fixes were backported to all branches eligible to receive security fixes, currently through 4.7, that only the most recent version is actively supported, and that the backports are in progress and will ship as they become ready. Also notes that sites with automatic background updates will begin the update process automatically. Checked November 19, 2026. The post does not assign CVE identifiers and does not report in-the-wild exploitation.
- Patchstack, WordPress 7.1.5 Security Release, November 18, 2026: article by Dave Jong. Says the release has twenty fixes, eighteen added to the Patchstack database as vulnerabilities and two treated as hardening changes with no exploitable path. Says no CVE identifiers had been assigned at the time of publication. Describes the Template Part issue as unauthenticated, with remote code execution possible once an editor opens the content; the WP_Meta_Query SQL injection as unauthenticated through a caller that passes request data into meta_query; and the stored XSS in comments as also depending on a page with a Latest Comments block. Says every branch back to 4.7 has a patched release, and that branches 4.6 and earlier no longer receive security updates. Checked November 19, 2026. The article does not report in-the-wild exploitation.
- WordPress.org, Version 7.1.5 documentation: official version page stating that WordPress 7.1.5 was released to the public on November 18, 2026, repeating the security-update list and the backport note. Checked November 19, 2026.