WordPress 6.9.3 was released on March 10, 2026, the same day as the 6.9.2 security release. It is a fast follow release that fixes a problem where some sites showed a blank front end after updating to 6.9.2.
What changed
According to the official announcement, the issue was traced to some themes that load template files through "stringable objects" instead of plain strings for file paths. The template_include filter only accepts a string, so this is not an officially supported approach, but it still caused some sites to break. The Security Team chose to address it right away in 6.9.3.
WordPress 6.9.3 also keeps all of the security fixes from 6.9.2. The same announcement introduced WordPress 7.0 Beta 4, an extra beta that includes the ten security patches so testers of the then upcoming major release stay protected.
How to update
The recommendation is to update to the latest version of WordPress immediately. Sites that support automatic background updates receive it on their own. You can also update from Dashboard, then Updates, then Update Now.
Theme template code lessons from the WordPress 6.9.3 fix
This is a good reminder of why theme code should stick to documented WordPress APIs. If your custom theme or a plugin filters template_include, it should return a plain file path string. We review custom themes for patterns like this during maintenance, because code that works by accident can break with a routine security update.
If your site went blank after 6.9.2, updating to 6.9.3 should restore it. If it does not, that points to a theme or plugin conflict worth investigating on staging.
Blank front end fix. A blank home page is about the most visible failure a site can have, and it can cost leads and sales until someone notices. On sites we manage, we check the live front end, not just the dashboard, right after every security update, so a problem like this is caught quickly. When we find a template_include filter that returns an object, we change it to return a plain file path so the site no longer depends on an unsupported pattern.
6.9.2 security fixes carried forward. Because 6.9.3 keeps every security fix from 6.9.2, you do not have to choose between a working site and a protected one. If a site broke after 6.9.2, we move it forward to 6.9.3 rather than rolling back to 6.9.1, which would reopen the ten issues 6.9.2 fixed.
WordPress 7.0 Beta 4 with the security patches. Test environments are still WordPress installs, and an unpatched beta on a public URL is an easy target. We run beta testing for clients only on staging copies, and we patch those copies on the same schedule as production.
Want WordPress 6.9.3 and every release after it handled for you? Our support and maintenance plans cover tested core, theme and plugin updates, uptime monitoring and help when something breaks. Questions about your site? Contact us and we will take a look.
