WordPress 7.1.5: 20 Security Fixes, What to Do Today
Admin
WordPress released version 7.1.5 on November 18, 2026, a security update with 20 fixes. Four of the flaws require no account on the site, and one of them could lead to code running on the server. The project recommends updating immediately. Every WordPress site is affected, including those on older branches.
What we know
- What shipped and when: WordPress 7.1.5 on November 18, 2026, according to the official WordPress.org post by Jeremy Felt. The post calls it a security release and recommends updating "immediately."
- How many fixes: both the post and the version page list 20 items. The post presents two as hardening (a malformed regular expression and the removal of the block editor's Imgur embed variation); the version page speaks of "all 20 vulnerabilities" and counts 17 changed files.
- No account needed: per the version page, a stored XSS through shortcode attributes in comments, a denial of service through batched XML-RPC pingbacks, disclosure of private taxonomy terms through the REST API search endpoint, and a privilege escalation through Template Part block attributes that "could lead to remote code execution."
- Account needed: those that state a role range from Subscriber to Administrator: XSS for Contributors, user email disclosure for Authors, authorship data for Editors. On multisite networks, a site Administrator could take over the Super Admin account. Five more (two SQL injections and three XSS) don't state the role required.
- What they don't say: neither page gives CVE IDs or severity scores, and neither mentions attacks in the wild.
- Who reported them: the post credits independent researchers, the WordPress Security Team and Anthropic, which reported two of the issues.
- Test release: per the post, 7.2 RC2 has also shipped with the applicable fixes.
- Older branches: fixes go to every branch that still gets security updates, down to 4.7. The version page lists 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12 and 6.5.15, among others; 4.6 and earlier get no fixes.
- Next: WordPress 7.2 is still planned for December 8, 2026, per the post.
What changes and what doesn't
- The minimum safe version changes: 7.1.5 on the 7.1 branch, and the new minor release on each older branch.
- The risk profile changes compared with October's 7.1.4: back then most flaws required a Contributor account or higher. This time several need no account at all, so having few users no longer lowers the priority.
- How you install it doesn't change: it is a minor release. Per the post, sites with automatic background updates will start updating on their own.
- Plugins are separate: 7.1.5 fixes WordPress core; plugins and themes update on their own.
How to tell if you're affected
- Check your version. In the WordPress dashboard, go to Dashboard → Updates. It also shows in the bottom right corner of admin screens.
- Confirm the automatic update landed. If you see 7.1.5, or your branch's fixed release (7.0.9, 6.9.12, 6.8.13…), you're done. If not, take a backup and click "Update Now."
- Don't wait because your site is small. The flaws that need no account hit a five-page brochure site as hard as a store.
- On a multisite network, review who is a site Administrator and who is Super Admin, and remove permissions nobody needs.
- On an older branch, install at least your branch's fixed release. On 4.6 or earlier there is no patch: plan the migration.
- If someone else runs your site (managed hosting or an agency), ask which version it runs today and when it was updated. Staging copies count too.
Related: WordPress 7.1.4 Security Release: What to Do Today
Sources
Updates: if WordPress publishes CVE IDs or reports attacks against these flaws, it will be added here with a link.
Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.