Updating WordPress to 7.1.4 Safely: A Blogger's Checklist

An exploited WordPress flaw lives in the update process itself, so updating to 7.1.4 needs one extra step. What the bug does, a five-step safe-update checklist, and signs to check.

Gurvinder SinghGurvinder SinghAuthor19 November 20264 min read 1 views
Updating WordPress to 7.1.4 Safely: A Blogger's Checklist
In this article▾
  1. What the flaw actually does
  2. Why clicking "Update" is the risky moment
  3. The safe-update checklist
  4. 1. Back up first
  5. 2. Block web access to wp-content/upgrade
  6. 3. Check the block works
  7. 4. Now update
  8. 5. Leave the block in place
  9. On managed WordPress hosting
  10. Already updated? Look for these signs
  11. The unglamorous part of owning your platform

If you run a self-hosted WordPress blog, you need to be on WordPress 7.1.4, released on 28 October 2026. That part is normal security advice. What isn't normal is that the flaw it fixes lives in the update process itself, so the moment you click "Update Now" is the moment your site is exposed. CISA added the bug to its list of actively exploited vulnerabilities on 3 November. The fix is still to update, but with one five-minute step first. Here's what's going on and a checklist that works on a VPS or ordinary shared hosting.

What the flaw actually does

WordPress described it in the 7.1.4 release post as "a weakness in the upgrade process which can lead to remote code execution during the upgrade window," credited to researcher Umut Bayram. His write-up for Picus Security explains the mechanism in plain terms.

During a core update, WordPress unpacks the new version into a folder under wp-content/upgrade/. That folder sits inside your website, so by default anyone on the internet can request files from it. The package includes WordPress's own installer. For a short window, an attacker who knows or can guess the folder name can open that installer, point the temporary copy at a database they control, log in, and run code on your server before WordPress cleans up.

The details that matter for a blogger:

  • Affected: Picus lists WordPress 2.7.0 through 7.1.3.

  • Fixed: 7.1.4, with the fix backported to every maintained branch down to 4.7. Versions 2.7 to 4.6 got no fix.

  • Exploited: CISA confirmed active exploitation on 3 November, and BleepingComputer reported Wordfence blocking 13,095 attacks against it in a single 24-hour period.

Why clicking "Update" is the risky moment

As Expert Insights explains, an update runs code from two versions. Your installed, still-vulnerable updater unpacks the package into the predictable folder; only then does the new code take over. So the update to 7.1.4 still uses the old staging behaviour. Only updates made after 7.1.4 use a random folder name.

And no, WP-CLI's wp core update doesn't get around it. Picus notes it uses the same updater.

The safe-update checklist

1. Back up first

Files and database. Your host's backup tool or your usual plugin is fine. You want a restore point from before the update.

2. Block web access to wp-content/upgrade

WordPress only needs to write to this folder on disk; it never needs to serve it to visitors. So you can block it from the web without breaking updates. Picus gives these rules.

On Nginx, in your site's server block:

location ^~ /wp-content/upgrade/ {
    deny all;
}

On Apache, in the virtual host configuration (adjust the path to your install):

<Directory "/var/www/html/wp-content/upgrade">
    Require all denied
</Directory>

On shared hosting where you can only edit .htaccess, add this to the .htaccess in your WordPress root, above the WordPress rewrite block:

RedirectMatch 403 ^/wp-content/upgrade/

One trap: don't put an .htaccess file inside the upgrade folder itself. The old updater empties that folder before unpacking, so your protection would be deleted just before it's needed.

3. Check the block works

Before updating, request the folder from outside and confirm you get a 403:

curl -I https://example.com/wp-content/upgrade/

Replace the domain with yours. If you see 200 or a directory listing, the rule isn't active yet.

4. Now update

Dashboard, then Updates, then Update Now. When it finishes, confirm the version at the bottom of the admin screen or under Dashboard, then Updates.

5. Leave the block in place

There's no reason to remove it. Future updates don't need the folder to be public either.

If you're comfortable with files and would rather not touch server config, Picus describes an alternative: extract the release outside the web root, copy in wp-admin, wp-includes and the top-level core files (never wp-config.php, never wp-content), then visit /wp-admin/upgrade.php to finish. It's more work and easier to get wrong, so most bloggers are better off with steps 1 to 5.

On managed WordPress hosting

If your host runs updates for you, you may not control any of this. Send them two questions: have you applied 7.1.4 to my site, and do you block public access to wp-content/upgrade? A good host will answer quickly. A vague answer is useful information too.

Already updated? Look for these signs

Picus doesn't publish a formal checklist, but based on how the attack works, these are worth a look if your site updated before you'd blocked the folder:

  • Administrator accounts you don't recognise, or plugins you didn't install.

  • A wp-config.php that changed recently or points to an unfamiliar database.

  • Leftover files under wp-content/upgrade/.

  • Requests in your access logs to /wp-content/upgrade/ paths, especially setup-config.php.

  • PHP files in your WordPress folders that you didn't put there.

If you find any of these, restore from a clean backup and change your passwords, including the database password. If you're not sure, ask your host's support team to check; this is exactly what you pay them for.

The unglamorous part of owning your platform

Independent publishing means owning your audience, your domain and your archive. It also means owning the patching. The same boring discipline that keeps your newsletter landing in inboxes, the SPF, DKIM and DMARC setup, keeps your blog online. Put a recurring reminder in your calendar to check for core and plugin updates, and while you're in the dashboard, our note on handling comment spam under Google's updated guidance covers the other thing attackers love about unattended blogs.

WordPress 7.2 is planned for 8 December, according to the release post. With the folder blocked, that update will be a non-event, which is exactly how updates should feel.

Keep reading

More from Gurvinder Singh

More from Gurvinder Singh

More in Guides & Tutorials

Have a story of your own?

Publisha is free to start. Write with AI that keeps your voice, and publish in a click.