The 4 November batch carries one record. CISA added CVE-2026-119977 to the known exploited catalog on 3 November with a due date of 6 November 1. A KEV row is CISA’s statement that someone used the bug. The race sits in the WordPress core upgrade process, and the affected range runs back to 4.7 2. One record and a deadline three days after the listing make the work a version inventory. I can read about the race in an afternoon; which sites sit on an old branch is the part that needs answers from other people.

What the entry says

The record is CWE-367, a time-of-check to time-of-use race in full-package core upgrades 2. The mechanism, the staged installer path and the code execution that follows are in the deep dive: CVE-2026-119977, the WordPress update runs through the window it fixes.

Two fields on the KEV row matter for the relay. The ransomware field reads Unknown, so I will not claim a ransomware link. The forensic triage field reads Yes 1, and the row’s required action cites BOD 26-04 and CISA’s Forensics Triage Requirements, which tells me the listing expects a look at the hosts as well as an update.

Who sits on an old branch

WordPress published 7.1.4 on 28 October as a short-cycle security release and said the fixes were backported to every branch still eligible for security fixes, with the backports shipping as they become ready and only the newest version actively supported 3. The current branch has a build; an older branch has a date that can move. A site on one of those branches should see the matching build on its own branch before anyone books a window for it, because a plan built on the release announcement can outrun the file.

The question I would put to each owner is small: what serves a public page, and which core version does it report. A host with shell access answers in one command, wp core version. A host without one answers from the dashboard footer or the Updates screen.

Attacks against the path

Wordfence’s threat-intel entry reported 14,312 attacks blocked in the past 24 hours when I loaded the page on 4 November 4. The figure is a rolling window from one vendor’s sensor network and counts attempts, not successes. The number still says people are pointing tools at the path.

What goes to the owners

6 November is the deadline on the federal side, and the relay that follows from it is short. Per host: the core version, whether the matching fixed build exists on that branch, who confirms the version after the update finishes, and whether the triage flag calls for a check on that host.

A public site on an old branch goes ahead of an internal one on the current branch, and the list keeps its value past this deadline. The next entry that names a platform everyone runs asks the same four questions, and the answers already exist once someone writes them down.


  1. Cybersecurity and Infrastructure Security Agency. (2026, November 3). Known exploited vulnerabilities catalog: CVE-2026-119977. U.S. Department of Homeland Security. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977 ↩︎ ↩︎

  2. National Vulnerability Database. (2026, October 31). CVE-2026-119977 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-119977 ↩︎ ↩︎

  3. WordPress. (2026, October 28). WordPress 7.1.4. WordPress News. https://wordpress.org/news/2026/10/wordpress-7-1-4/ ↩︎

  4. Wordfence. (2026, October 31). WordPress core 4.7.0 - 7.1.3 - Unauthenticated upgrade-window staged-installer remote code execution. Defiant. https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution ↩︎