After updating a custom-template site to WordPress 7.1.2, check Site Health, theme and plugin status, front-end template pages, and the PHP error log. A custom template is a theme file that controls the layout of specific pages, and this update changed how WordPress resolves those files. WordPress released version 7.1.2 on September 22, 2026 as a security release for one critical vulnerability, according to the WordPress 7.1.2 release announcement. The flaw let an unauthenticated attacker steer page-template resolution toward a chosen readable local PHP file outside active theme directories, with possible remote code execution when server and theme conditions were met.
Table of Contents
- Why custom templates need closer checks
- Confirm the update finished cleanly
- What should Site Health show?
- How to catch template errors without alarming visitors
- Frequently Asked Questions
Why custom templates need closer checks
Sites with custom page templates, child themes, or template-selection plugins face the most exposure. The issue is tracked as CVE-2026-87902 and was backported through version 4.7, so older-branch sites with custom templates were affected too. Patched resolution may block a previously working template path or reveal a fragile include.
Check layouts that rely on assigned templates first, not only the homepage. Compare portfolio pages, landing pages, custom archives, and one-off sales pages. Look for blank sections, wrong layouts, missing sidebars, or unexpected default-template fallback.
Confirm the update finished cleanly
Start under Dashboard > Updates and confirm WordPress shows the intended version with no pending core files. Install remaining theme and plugin updates afterward, then visit the site to confirm pages load, according to the WordPress updating guide.
Keep a pre-update backup until these checks pass. Use a short pass readers can scan:.
- Confirm the core version and pending updates under Dashboard > Updates.
- Update themes and plugins, then reload cached pages in a private window.
- Open menus, forms, search, checkout, and other template-dependent actions.
- Note any page that changed layout, slowed down, or shows an error.
What should Site Health show?
Open Tools > Site Health and review the Status tab for critical issues, recommended improvements, and passed tests, according to the Site Health documentation. Fix critical items before recommended ones. Re-run the screen after each fix to confirm the warning clears.
Then open the Info tab for WordPress, theme, and server details. Confirm the active theme name and version, PHP version, server software, and directory paths. Save or screenshot this page when supporting several client sites.
How to catch template errors without alarming visitors
Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php so PHP errors, notices, and warnings go to wp-content/debug.log. Set WP_DEBUG_DISPLAY to false so visitors do not see those messages, according to the WordPress debugging guide. Review the log after loading each major template once.
Treat repeated entries naming the same template file, function, or plugin as the repair list. Disable debug logging after the review period to keep the log small. WordPress 7.1.4 from October 28, 2026 is now the maintained release in the series, so plan that follow-up update after monitoring settles.
Frequently Asked Questions
Do sites on older WordPress branches need the same template checks?
Yes. The fix was backported through version 4.7, so custom-template sites on older supported branches should run the same front-end and log checks after patching.
When should the debug log be turned off?
Turn it off after template pages load cleanly and Site Health shows no critical issue. Leaving it on can create a large log file on busy sites.
