With WordPress 7.1.5, the WordPress project has shipped a security release that fixes 20 issues in the core of the content management system. The most serious flaw can, under certain conditions, let an unauthenticated attacker create an administrator account through manipulated Template Part block attributes and use it to run code on the server. The update was released on November 18, 2026 and backported to all older branches. Since most installations apply minor updates automatically, the majority of sites are probably protected already. Anyone who has disabled automatic updates or manages versions manually should check now.
WordPress 7.1.5 at a glance
According to the official announcement, 7.1.5 is a security-only release. The list has 20 entries, including one hardening change without a specific vulnerability. For 19 of them, the project has published GitHub Security Advisories in the wordpress-develop repository. These advisories rate five issues as high, five as medium and nine as low severity. So far they include no CVE IDs or CVSS scores.
For comparison, WordPress 7.1.4 also closed a sizable batch of flaws at the end of October. Security releases are coming at a fast pace right now: only three weeks passed between 7.1.4 and 7.1.5. According to the release notes, two of the current flaws were reported by Anthropic.
The Template Part flaw in detail
The most critical vulnerability is described in security advisory GHSA-pmp8-6cv8-q323: a Template Part block’s “theme” and “slug” attributes could make an administrator’s editor send requests to another URL on the same site. Any user with the Author role or above could set these attributes in a post. An unauthenticated attacker could also send an administrator a crafted editor link or redirect them to one.
When the administrator opened it, this could create an administrator account for the attacker. With administrator rights, WordPress allows code execution through plugin upload. According to the advisory, all versions from 5.9, which introduced the Template Part block with the site editor, are affected. The fix is in 7.1.5 and in the backported releases down to 5.9.21. The flaw was reported by Logan Homolka.
For context: an attack requires a logged-in administrator to open a manipulated link. It does not work without user interaction. Phishing emails to editorial teams and agencies, however, are a realistic way to achieve exactly that. The WordPress project does not mention any active exploitation.
The other high-severity issues
Besides the Template Part flaw, the project rates four more issues as high:
- Stored XSS via shortcode attributes in comments: unauthenticated attackers could plant malicious code in comments.
- Reflected XSS in the legacy media library popup: reported by Anthropic.
- XSS in the block editor via Openverse image metadata: crafted metadata of openly licensed images could inject scripts.
- Privilege escalation in multisite networks: a site administrator could take over a Super Admin account through Customizer menu previews.
Rated medium are, among others, two SQL injections, one in WP_Meta_Query via nested “relation” values and one via the front page setting in Customizer changeset previews. There is also an unauthenticated denial of service via batched XML-RPC pingbacks, disclosure of private taxonomy terms via the REST API search endpoint, also reported by Anthropic, and comment disclosure via XML-RPC for subscribers.
The low-severity items are mostly XSS variants that already require Contributor, Author or Editor rights, for example via oEmbed responses, the Comment Date block’s date format or file names when converting a media block. They also include disclosure of email addresses via the REST API comments endpoint and hardening of JSON media type matching. The update also removes the Imgur embed variation from the block editor, whose provider endpoint no longer exists.
Which versions are protected
The project backported the fixes to all branches still receiving security updates. The version documentation and the release list include these versions from November 18:
- 7.1.5 (current branch)
- 7.0.9
- 6.9.12
- 6.8.13
- 6.7.12 and further older branches
According to WordPress, only the latest version is actively supported. Sites still on an old branch get the fixes as a courtesy but should plan an upgrade anyway. In 6.9.12 and earlier, the update also removes 1024-bit certificates from the bundled root certificates, as already happened in 7.0.
The next major version, WordPress 7.2, is planned for December 8, 2026. According to the announcement, the second release candidate contains all applicable fixes.
What site operators should do now
- Check the version: in the dashboard under “Updates” or via WP-CLI with
wp core version. You should see 7.1.5 or the matching release of your branch. - Verify automatic updates: minor security updates are enabled by default. If you disabled them via constants such as
WP_AUTO_UPDATE_COREor plugins, update manually. - Review user accounts: new, unknown administrator accounts are a red flag, especially given the Template Part flaw.
- Consider XML-RPC: if you do not need the interface, blocking it reduces the attack surface, for example against the pingback issue.
- Brief your editors: administrators should not open editor links from unknown sources.
Agencies and others who manage many installations can query versions across servers with WP-CLI and use wp core update --minor to apply only the security update within their branch without jumping to a new major version. As always, back up files and the database first, even though security-only releases rarely cause compatibility problems. Plugins and themes are not covered by 7.1.5 and need to be kept up to date separately.
How quickly core flaws can become relevant was shown recently by WordPress flaw CVE-2026-119977, which was added to CISA’s catalog of actively exploited vulnerabilities. On the server side, version levels are worth checking too, for example after the latest PHP security updates.
Bottom line: WordPress 7.1.5 is no reason to panic, but it is a mandatory update. Most of the flaws require user rights or an administrator’s click. The combination of the Template Part flaw and phishing, however, makes the update urgent for any site with several editors or public comments.




