Skip to main content
Published on November 16, 2026
CVE-2026-119977 — WordPress core, versions 4.7 to 7.1.3. During a full core update, an unauthenticated attacker can run code on the server. CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 3, 2026. WordPress 7.1.4 fixes it, and the fix was backported to every branch down to 4.7. Check the version of each site today.

The bug in two sentences

When WordPress updates its core from the full package, it extracts the new files to a predictably named directory inside the upgrade folder served by the web server. An attacker who wins the race against that extraction can execute code remotely, with no account on the site. It is a time-of-check time-of-use race condition (CWE-367): the attack window is the length of the update. Wordfence, which assigned the CVE, scores it 8.1 under CVSS 3.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H); NVD carries the same score. Attack complexity is high: the attacker has to hit the update window. Red Hat rates it “Important”. The WordPress project, in its advisory GHSA-4w3m-c66w-69mg, rates it “Low”. Umut Bayram (Picus Security) found the flaw. WordPress 7.1.4 shipped on October 28, 2026.
A KEV entry means exploitation has been seen on real systems. That, more than the gap between scores, should set your priority.

Sizing your exposure

The question to ask: does every one of your sites run the fixed version of its branch? Fixed versions, per the WordPress project’s advisory: To find a site’s version:

Updating WordPress per install type

The WordPress project’s advisory lists no workaround: the core update is the fix.

WordPress installed by hand or with WP-CLI

Sites that support automatic background updates receive the fix on their own. Check the version anyway: a site with automatic updates turned off, or with read-only core files, stays where it is.
From the admin area, the update is under Dashboard → Updates → Update Now.

cPanel web hosting

On OnetSolutions web hosting, Softaculous shows an update button for every installed application that has one. It is the fastest way to check several sites at once.

Debian and derivatives (wordpress package)

RHEL and AlmaLinux (EPEL wordpress package)

WordPress is not shipped in RHEL’s repositories. The wordpress package comes from EPEL, which carries 6.9.11 (EPEL 9 and EPEL 10.2) and 7.1.4 (EPEL 10.3 and 10.4), all fixed.

Checking the fix

wp core verify-checksums reports any modified or added core file. Since the flaw is being exploited, review the administrator accounts too:
An unknown account or a modified core file: treat the site as compromised, restore an earlier backup, update, then rotate every password.

What next?

Automatic minor updates carry the core’s security fixes: keep them on, as our WordPress hardening checklist explains. On a VPS, also turn on automatic security updates for system packages. For another recent flaw, read the APT vulnerability CVE-2026-109518. For any technical question, open a ticket from your OnetSolutions customer area.