WordPress 7.1.4: The Security Update Your Website Needs Today (Including an Upgrade-Process Flaw)

If your company runs its website, online store or blog on WordPress, today is the day to check the dashboard. On October 28, 2026 the project released WordPress 7.1.4, a security release that it recommends installing immediately. One of its fixes stands out: a weakness in the upgrade process that can lead to remote code execution during the upgrade window.
What WordPress 7.1.4 fixes
The official announcement lists 12 security fixes (the Interactivity API entry groups several flaws, so the number of individual issues is higher). These are the main ones, as the project describes them:
- A weakness in the upgrade process that can lead to remote code execution during the upgrade window. The notice credits Umut Bayram and gives no further technical details.
- Several stored XSS flaws (malicious code saved on the site that runs in the browser of whoever visits or administers it): in blocks with crafted markup, in privacy data removal requests, in the Interactivity API, in Customizer selective refresh, in the Categories block, in crafted user logins, in playlist and image blocks, and in the comments-pagination blocks.
- A stored denial-of-service flaw in the Interactivity API.
- Unpublished Customizer changes that could be seen without logging in.
- Notes readable by privileged users who cannot edit the attached post.
The release also includes a root certificate update tied to the eMudhra revocation.
Which versions get fixed?
The notice does not specify which versions are affected, but it does say the fixes are being backported to all branches eligible for security fixes, currently through 4.7, and that those patches will ship as they are ready. In other words: if your site is on a version older than 7.1, do not wait to "jump" versions; look for the security update for your branch. And if your site is on a version that no longer gets patches, it is time to plan a migration. According to the announcement, WordPress 7.2 is planned for December 8.
What to do today: a 20-minute checklist
- Back up files and database before touching anything, and make sure you can restore it.
- Update from Dashboard → Updates → "Update Now", or download the release from WordPress.org. Sites with background automatic updates will start updating by themselves; check that they did.
- Confirm the installed version (Dashboard → Updates, or the footer of the admin panel).
- Update pending plugins and themes. An up-to-date core with an abandoned plugin is still a risk.
- Review administrator users. Remove accounts that are no longer used and enable two-factor authentication for the rest. Several of the fixed flaws are XSS issues that abuse privileged accounts.
- Check your test environment. If you have a staging site, update it too.
What this means for your business
For a small company, the website is often the first impression and the channel that receives quote requests, bookings or orders. A compromised site can do more than show someone else's content: it can redirect your customers, steal form data or damage your search reputation. The good news is that updating is cheap compared with recovering from an incident. The bad news is that many small businesses have nobody responsible for it: a vendor built the site years ago and nobody touches it.
- Assign an owner (internal or external), with a name, for site updates.
- Enable automatic security updates for the core, and schedule a monthly plugin review.
- Keep backups off the server and test restoring them at least twice a year.
- Cut plugins. Every extra plugin is third-party code to maintain; uninstall the ones you do not use.
For developers and site administrators
If you manage several sites, take the chance to automate: WP-CLI lets you update the core and check versions in bulk, and continuous integration with visual tests helps catch breakage after updating. Also check that your installations' upload and upgrade directories have minimal permissions, and that the server does not execute code from folders where WordPress should only store files. If you use PHP, do not forget this month's critical PHP fixes: an up-to-date WordPress on an unpatched PHP is still exposed.
How we approach it at SimCodec
At SimCodec we design and maintain websites for companies with a practical approach: scheduled updates, verified backups, plugin reviews and monitoring. If you do not know who updates your site or when it was last done, write to us and we will review your case, or call our AI assistant Cyntia at +593 99 726 6838. If you are evaluating providers, this guide on how to choose an IT provider can help you ask the right questions.
Sources
- WordPress.org: WordPress 7.1.4 Security Release (October 28, 2026)


