Two weeks ago we wrote about PHP2Shell, a flaw in PHP that updating WordPress could not fix. This time the flaw is in WordPress itself. The fix shipped on 28 October in version 7.1.4, and on 3 November the US cybersecurity agency CISA added it to its list of vulnerabilities exploited in the wild.

The good news: this time, updating WordPress is enough. The bad news: not every site has updated itself.

What happened

The flaw is tracked as CVE-2026-119977 and rated 8.1 out of 10. It affects WordPress 4.7 through 7.1.3, which is effectively every release of the last nine years.

The problem was in the WordPress update process. During an update, WordPress unpacked the new version into a temporary folder whose location was predictable and reachable from the internet. An attacker who reached that folder at the right moment could run the WordPress installer there and write a new configuration file. At the end of the update, WordPress copied that file onto the live site along with everything else.

The forged configuration file points the site at the attacker's database. From there the attacker can log in as an administrator, install their own plugins and run any code on the server. No login or user account is needed.

The attacks have started. WordPress security firm Wordfence reported blocking more than 13,000 attempts against this flaw in a single day.

Why this one is different

Normally the site at risk is the one that has not been updated. This hole opens during the update itself, in the moments while WordPress installs the new version. Attackers do not know when you will update, and they do not need to. Their bots keep knocking and wait for the door to open.

Does that make updating dangerous? No. The WordPress security team built the fix so that its most important part arrives with the new version and already protects the very update that installs it. Updating now is still the right move.

How to check your WordPress version

Log in to WordPress. The version number is in the bottom right corner of the dashboard, for example "Version 7.1.4". For more detail, open Dashboard → Updates.

On the current branch you need at least 7.1.4. WordPress also backported the fix to older branches all the way down to 4.7: fixed versions include 7.0.8, 6.9.11, 6.8.12 and 6.7.11. If you are on an older branch, the WordPress security advisory lists its fixed version.

Keep in mind that WordPress officially supports only the latest version. Backports to older branches are a courtesy, and they may not come for the next flaw.

Why the automatic update may not have run

WordPress installs security releases on its own by default. That does not mean every site is up to date. The usual reasons:

  • Automatic updates are switched off. Developers often do this so an update cannot break a plugin or theme, and then it is forgotten for years.
  • Server file permissions do not let WordPress change its own files.
  • A plugin or a hosting setting blocks updates.
  • The site gets few visitors. WordPress runs its scheduled tasks when someone visits, so a quiet site can wait days for an update.

You can check the state of updates under Tools → Site Health. If background updates are not working, WordPress says so there.

How to tell whether the site has been hacked

A hacked site can look completely normal to visitors. Check for these:

  • An administrator in the user list you do not recognise.
  • A plugin you did not install.
  • A changed database address (DB_HOST) in wp-config.php. You can open the file in your hosting file manager.
  • Requests in the server logs to an address containing both wp-content/upgrade and setup-config.php. Normal operation never requests that address.

If you find anything suspicious:

  1. Do not delete anything yet. First take a copy of the site and the server so you can find out later what happened.
  2. Restore the site from a clean backup taken before the suspicious update.
  3. Change every password: WordPress users, the database, hosting and FTP. Also change the security keys in wp-config.php so that every existing login stops working.
  4. Update WordPress, the plugins and the theme.
  5. If the site holds customer data, such as orders or contact form messages, you may be required to report the breach to your data protection authority within 72 hours. In Estonia that is the Data Protection Inspectorate (Andmekaitse Inspektsioon).

For server owners: lock the door

If you run your own server, block web access to the /wp-content/upgrade/ folder. Nothing ever needs to reach it over the web, and blocking it also protects against similar flaws later. In nginx that is location ^~ /wp-content/upgrade/ { deny all; }; in Apache, a Require all denied rule for the same folder.

The fourth WordPress core flaw this year

Before this July, CISA's list of exploited vulnerabilities held no WordPress core flaws at all, only plugins. Now it holds four: two in July, one in September and this one. Then there was PHP2Shell in October, which was not a WordPress flaw but hit every WordPress site.

WordPress is not bad software. It is simply so widespread that every flaw pays off for attackers. A WordPress site needs ongoing maintenance, not a one-off build.

A free WordPress check

Tuumpiksel will check your site for free, wherever it is hosted. We find out which version it runs, whether automatic updates work, and whether there are signs of an intrusion.

If the site needs an update, we run it on a staging copy first so the live site keeps working without interruption. If we have no access to the server, you get precise instructions for what to ask your provider.

If maintenance starts to cost more than the site is worth, we calculate the price of a new site as well. We build with Nuxt and Next.js (Payload CMS), neither of which uses WordPress or PHP.

Order the free check →