WordPress CVE-2026-119977: remote code execution during core updates

Venus Yazılım4 min read

WordPress 4.7 to 7.1.3 can be attacked during core updates without logging in. Update to 7.1.4 or 7.0.8. Older branches: see the WordPress.org notice.

A WordPress site stays exposed for a short time while its core is being updated. This flaw targets exactly that window. Update your site this week and confirm the version afterwards.

Short answer: CVE-2026-119977 is a WordPress core flaw that allows code execution without authentication during a core update. The NVD record lists versions 4.7 through 7.1.3 as affected. The fixed releases are 7.1.4 and 7.0.8. For older branches, check the WordPress.org announcement.

At a glance

Item Detail
CVE CVE-2026-119977
CVSS v3.1: 8.1 (High). The NVD record has no v4.0 score
Flaw type Race condition (TOCTOU, CWE-367): the state can change between a check and the use that follows
Authentication required No
Active exploitation CISA confirmed active exploitation and added the flaw to KEV. Wordfence reports it is seeing exploitation attempts
CISA KEV added 3 November 2026 (federal agencies were due to patch by 6 November 2026)
Fixed versions 7.1.4 and 7.0.8. Older branches: see the WordPress.org notice

What happened?

When WordPress updates its core from a full package, it unpacks the new files into a temporary folder that is reachable from the web. The path to that folder follows a predictable pattern. Because the path can be guessed, an attacker can try to place files there while the update is running.

The flaw is a TOCTOU (time-of-check to time-of-use) race condition. That means the state of something can change between the moment it is checked and the moment it is used. The update window is short, so an attacker has to hit it. No account is needed.

WordPress 7.1.4 also fixes several stored XSS issues and an information exposure problem. The update is worth applying for those fixes as well.

Who is affected?

  • Affected: WordPress versions 4.7 through 7.1.3, according to the NVD record. Sites that run full-package core updates are the main concern.
  • Fixed: 7.1.4 (the 7.1.x branch) and 7.0.8 (the 7.0.x branch).
  • Older branches: The WordPress.org announcement says active security support covers only the most recent release. It asks you to check WordPress.org for older branch releases.

What should you do?

  1. Check your version. With WP-CLI, run wp core version. Without it, run grep "wp_version =" wp-includes/version.php from the WordPress root. You can also check Dashboard > Updates.

  2. Back up first. Take a backup of your files and database before you update.

  3. Update. You can update from Dashboard > Updates, or with WP-CLI:

wp core update
wp core verify-checksums

verify-checksums reports core files that differ from the official release. If you are on a branch other than 7.1.x or 7.0.x, confirm the fixed release for your branch on the WordPress.org announcement.

  1. Confirm the new version. Run wp core version again and check for 7.1.4, 7.0.8, or the fixed release for your branch.

  2. Interim measures. The sources do not describe any workaround besides updating, so do not delay the update.

Have I been hit?

The sources list these indicators of compromise (IoCs):

  • Requests in your access logs for setup-config.php. Wordfence and The Hacker News both report this traffic.
  • Requests to the predictable, web-reachable staging paths that full-package core updates use, as CISA describes them.

The sources do not publish the full paths, so search your logs for these requests. Also check the following:

  • Does wp core verify-checksums report any modified core files?
  • Does wp user list --role=administrator show an administrator account you do not recognize?
  • Are there PHP files in the web root that you did not put there?

Frequently asked questions

How do I know whether I am in the 4.7 to 7.1.3 range?

Run wp core version or read the version number in wp-includes/version.php. If the number falls in that range, you need to update.

My host says it updated WordPress. Should I still check?

Yes. Confirm the version yourself. The check takes seconds.

I have to stay on an older branch. What now?

Find the fixed release for your branch in the WordPress.org announcement and apply it. Release status can change, so check the announcement again before you rely on it.

Sources

To keep your WordPress site patched and monitored, see our CMS service.

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 5 min read

    Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

    Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address