Skip to content
Techzovia
Tech News

CISA says a WordPress updater flaw is being exploited: update to 7.1.4

CISA has added a WordPress core remote code execution flaw, fixed in 7.1.4, to its list of exploited vulnerabilities. Here's how to check and update your sites.

By Golam Moktadir3 min read
On this page

On November 3, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-119977 to its Known Exploited Vulnerabilities (KEV) catalog. The flaw is a remote code execution bug in WordPress core, and WordPress fixed it in version 7.1.4 on October 28. If you run a WordPress site, check today that it is on a patched version.

What happened

WordPress 7.1.4 was a security release. Its release notes list 12 security fixes plus an update to the bundled root certificates. The most serious fix, credited to researcher Umut Bayram, is for a weakness in the upgrade process. WordPress says it could allow remote code execution while an upgrade is running. BleepingComputer reports that Bayram works at Picus Security.

The CVE record was published on October 31, with Wordfence as the assigning authority. It classifies the bug as a time-of-check/time-of-use race condition and gives it a CVSS 3.1 score of 8.1 (High). According to the record, an unauthenticated attacker can run code through predictable, web-accessible staging paths that WordPress uses during full-package core upgrades. Every release from 4.7 through 7.1.3 is listed as affected.

Two days after the record went public, CISA added the flaw to the KEV catalog, and its entry on the CVE record marks exploitation as active. BleepingComputer reports that U.S. federal civilian agencies must patch by Friday, November 6. It also reports that Wordfence said it blocked 13,095 attacks against the flaw in a single 24-hour period. CISA has not said who is behind the attacks.

Why it matters

The vulnerable moment is the update itself. Attackers go after the short window when WordPress unpacks the new version, so a site is exposed while it updates from an affected release. The CVE record rates the attack complexity as High, which means an attacker has to get the timing right. CISA's listing and the Wordfence numbers suggest people are trying anyway, at scale.

The affected range goes back to 4.7, so old, rarely touched sites are included. WordPress says it is backporting the fixes to every branch that still gets security updates, back to 4.7. Those backports were still in progress when 7.1.4 was announced. The official releases page already lists 7.0.8 for the 7.0 branch, dated the same day as 7.1.4.

Most of the other fixes in 7.1.4 close stored cross-site scripting holes, for example in the Interactivity API, the Customizer and several blocks. Even apart from the exploited bug, the release is worth installing.

WordPress says sites that support automatic background updates will start updating on their own. Hosts, plugins or configuration settings sometimes turn automatic updates off, though, so don't assume a site has updated until you've checked it.

What you should do

  1. Check the version. In the WordPress admin, go to Dashboard > Updates. The page shows the version you are running and whether a newer one is available. If you have shell access with WP-CLI installed, run wp core version.
  2. Take a backup first. Back up the files and the database before any core update. If you don't have a routine yet, start with our guide to the 3-2-1 backup rule.
  3. Update. Go to Dashboard > Updates and click Update Now. WordPress says you can also download 7.1.4 from WordPress.org and install it by hand. With WP-CLI, run wp core update, then wp core version to confirm the new number. If you manage servers over SSH, key-based login makes this quicker and safer.
  4. Older branches. If you can't move to 7.1 yet, check the WordPress releases archive for the newest release on your branch. Plan the upgrade as well: WordPress says only the most recent version is actively supported.
  5. Check every install. Staging copies, old subdomains and test sites all count. Any of them running an affected version can still be attacked.

WordPress's own advice in the release post is short: "it is recommended that you update your sites immediately."

Sources

Liked this guide? Get the next one by email

The best new tutorials and guides, a few times a month. Unsubscribe any time.

We'll email you a link to confirm. See our privacy policy.