Technology & security · · 8 min read · By Alexander
WordPress 7.1.5: What you should do about the Template Part vulnerability
WordPress 7.1.5, released on 18 November 2026, fixes a vulnerability in Template Part block attributes. It may allow privilege escalation and potentially remote code execution. Patchstack rates it at CVSS 9.6. An attacker does not need a WordPress account, but a logged-in user with editing permissions must open the manipulated content in the editor. Check the installed version of WordPress Core now and install the appropriate security release. This information reflects research carried out on 19 November 2026.

What happened?
The vulnerability affects attributes of the Template Part block. Manipulated values can change the destination of a request that the editor sends to WordPress. WordPress describes privilege escalation with possible remote code execution and credits Logan Homolka with discovering the issue.
The vendor’s list for the security release of 18 November contains 20 entries, including hardening measures. The release fixes further security issues, including a separate Multisite privilege escalation. The older Core Updater vulnerability involved an attack during an update. The new Template Part vulnerability does not require a Core update to be in progress.
How serious is the vulnerability?
The CVSS 9.6 severity score comes from Patchstack. The sources reviewed do not provide evidence of a score from WordPress or a CVE Numbering Authority (CNA). The CVSS version and full vector are not stated in the Patchstack data reviewed. No CVE identifier has been published in the primary sources examined, and an associated GitHub Advisory identifier (GHSA) has not been verified.
According to Patchstack, the attacker must deliver manipulated block content to a logged-in user who opens it in the editor with editing permissions. The editor sends the modified request using that user’s session. For the described route to code execution through plugin installation endpoints, the victim’s administrator rights are relevant. An Editor does not automatically have these rights. User interaction therefore remains necessary.
The sources reviewed do not confirm active exploitation of this new vulnerability. A corresponding entry in CISA’s Known Exploited Vulnerabilities (KEV) catalogue has not been established either. The existing WordPress entry concerns the older Core Updater issue. This is not an all-clear. Conversely, a high score or a vulnerable version does not prove that your website has been breached.
Which WordPress versions contain the security fixes?
Patchstack generally lists WordPress Core up to and including 7.1.4 as affected and 7.1.5 as fixed. For older branches, WordPress lists the following security releases in the release package. A backport is a fix for an older version branch. The list contains the applicable fixes, but does not map every individual issue exhaustively to every branch. A corrected older branch must therefore not be regarded as still vulnerable solely because its version number is lower. Compare versions within your branch:
- 7.1.5; 7.0.9; 6.9.12; 6.8.13; 6.7.12
- 6.6.12; 6.5.15; 6.4.15; 6.3.15
- 6.2.16; 6.1.17; 6.0.19; 5.9.21
- 5.8.20; 5.7.22; 5.6.24; 5.5.25
- 5.4.26; 5.3.28; 5.2.31; 5.1.29; 5.0.32
- 4.9.36; 4.8.35; 4.7.40
Only the latest WordPress version is actively supported. Backports do not offer an equivalent long-term support commitment. According to the vendor’s documentation, WordPress 4.6 and older versions no longer receive security updates. For an older branch, ask for the vendor evidence covering the installed backport. The list does not provide a security guarantee for your entire website.
How can I check whether my website is affected?
Check the Core version under “Dashboard → Updates”. Alternatively, if available, you can find it under “Tools → Site Health → Info → WordPress”. Compare the number with the security release for your branch. A green Site Health indicator does not confirm this patch. Before starting an update yourself, back up the files and database and clarify how they can be restored. Start the offered Core update via “Update Now”, wait for it to finish and then check the version again.
With Managed Hosting, use the intended update process or ask the provider to carry it out. WP Toolkit may be available under “WordPress” in Plesk and under “WordPress Management” in cPanel; this depends on the hosting service. Check the installed version even after automatic updates. Technical administrators can check from the correct WordPress directory using `wp core version` and `wp core check-update --minor`. After the backup, `wp core update --minor` updates within the existing branch. Then run `wp core version` again.
A completely static website without a WordPress installation does not contain the affected code. With a static export, any existing WordPress editorial system must still be checked and updated separately. A cache or static frontend does not prove that no WordPress Backend is still in operation.
In a Multisite network, the responsible Super Admin or hosting provider should arrange the Core update via “Network Admin → Dashboard → Updates”. If WordPress then requests a network update, run “Update Network”. The release also fixes a separate privilege escalation through Customizer menu previews that can allow a Site Administrator to take over a Super Admin account.
What should I write to my hosting provider or agency?
Copy the following enquiry and complete the placeholders:
“Subject: Check WordPress security update 7.1.5. Hello, please check the WordPress installation at [Domain]. Core version shown: [Version / unknown]. Please confirm the Core version actually installed after the update and the time the work was completed. For an older version branch, I require the vendor evidence for the backport and confirmation that it covers this vulnerability. Which backup of the files and database can be used, and how would it be restored? Does the check cover other installations and, where applicable, the entire Multisite network? After the update, please check the login, editor, navigation, forms, any shop functions and relevant Multisite subsites. Please send me the result. If the update is still pending, please state the reason, planned date and interim measure put in place. Thank you, [Name / customer number]”
Check the version again once the work is complete. The functional check is a general operational check after the update, not an investigation into a previous breach.
What if the update cannot be installed immediately?
The WordPress notice reviewed does not publish a workaround confirmed for all affected configurations. The update remains the main measure. Until then, the team maintaining your site can suspend the editing of third-party or unknown content and restrict access to the editorial system. The hosting provider must assess the installation to determine whether temporary isolation is necessary and feasible. These interim measures are not a complete fix.
Patchstack states that it has provided a mitigation rule. This does not establish a publicly verifiable rule identifier or confirm that the rule is active on your website. Ask the provider to confirm the rule that is actually active and its coverage of this specific vulnerability. The sources used do not demonstrate a specific Cloudflare rule for this Template Part vulnerability. Having a Cloudflare or WAF account alone does not support a claim of protection.
Disabling a single plugin, the visible Template Part block or XML-RPC alone is also not a confirmed comprehensive workaround. A static maintenance screen likewise does not demonstrate that the WordPress instance has been isolated. Have the outstanding Core security release installed promptly and check it afterwards.
Frequently asked questions about the WordPress Template Part vulnerability
My plugins are up to date – is that enough?
No. The confirmed fix is in WordPress Core. Current plugins, themes or a new PHP version do not replace the appropriate Core security release.
Does the attacker need a WordPress account?
According to Patchstack, the attacker does not need an account of their own. However, a logged-in user with editing permissions must open the manipulated content in the editor. Administrator rights of the affected user are relevant to the described route to code execution.
Am I safe with Cloudflare or a WAF?
The sources do not demonstrate a specific Cloudflare rule for this vulnerability. For Patchstack’s mitigation rule, ask for confirmation that it is active and covers your installation. This does not provide a general security guarantee; the Core update is still required.
Is a static website affected?
A purely static website without a WordPress installation does not run the affected code. With a static export, any WordPress editorial system that still exists must be checked and updated separately.
What do I need to consider with Multisite?
Have the Core update carried out across the network by a Super Admin or hosting provider, and complete any network update requested afterwards. The release also fixes a separate privilege escalation from Site Administrator to Super Admin.
Has my website already been hacked?
This cannot be inferred from the score or an old version. The sources reviewed do not confirm active exploitation of this new vulnerability. Conversely, the absence of evidence of exploitation does not prove that no attacks are taking place anywhere in the world.