The US Cybersecurity and Infrastructure Security Agency (CISA) has added a WordPress Core vulnerability to its Known Exploited Vulnerabilities (KEV) catalog, saying the listing is based on evidence of active exploitation.
In an alert dated 3 November 2026, CISA named CVE-2026-119977 as a WordPress Core time-of-check time-of-use (TOCTOU) race condition vulnerability. The same entry appears in CISA's KEV catalog and in the agency's published KEV CSV.
“CISA has added one new vulnerability to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation.”
CISA alert, 3 November 2026
Background
WordPress had already shipped a fix for an upgrade-window remote code execution weakness nine days earlier. On 28 October 2026, Aaron Jorbin announced WordPress 7.1.4 as a security release and said: "Because this is a security release, it is recommended that you update your sites immediately."
Among the fixes credited in that announcement is "a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram." The HelpHub page for Version 7.1.4 describes the same issue as "a race condition during core updates that could lead to remote code execution."
WordPress also said the 7.1.4 security fixes were being backported to older branches still eligible for security updates, and that WordPress 7.2 Beta 3 was released with the applicable fixes.
What CISA says the flaw allows
According to CISA's KEV description for CVE-2026-119977, WordPress Core contains a TOCTOU race condition that could allow unauthenticated attackers to execute code on the server during the upgrade window. CISA attributes that risk to "predictable, web-accessible staging paths used during full-package core upgrades." The catalog lists the related weakness as CWE-367.
CISA's catalog entry records the date added as 3 November 2026 and a due date of 6 November 2026. The entry also marks forensic triage as required under Binding Operational Directive (BOD) 26-04. In its 3 November alert, CISA says BOD 26-04 establishes vulnerability management requirements for Federal Civilian Executive Branch (FCEB) agencies and requires those agencies to prioritise rapid remediation of high-risk KEV vulnerabilities on publicly exposed assets.
That federal due date applies to covered US federal agencies under BOD 26-04. It is not a CISA deadline for every WordPress site worldwide. CISA's alert does say that, while BOD 26-04 applies only to FCEB agencies, the agency "encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities."
What site owners should do
WordPress's own advice remains the practical one for private and commercial sites: update to 7.1.4, or to the matching patched release for your branch once the backports are available. On sites that support automatic background updates, WordPress says the update process will begin automatically.
CISA's notes for the CVE point to the WordPress 7.1.4 news post and to a Wordfence threat-intelligence page as related references. Wordfence's public pages could not be retrieved reliably for this report, so no Wordfence traffic figures or extra technical claims are repeated here.
This report does not include exploit steps. At a high level, the risk CISA and WordPress describe is confined to the core upgrade window and to race conditions around staged installer paths that are web-accessible during a full-package upgrade.
What this means for site owners
Analysis by Depakar B
A KEV listing after a patch has already shipped usually means two things for operators: the vendor fix is the first line of defence, and anyone who delayed 7.1.4 should treat the update as overdue rather than optional. For US federal agencies covered by BOD 26-04, CISA's 6 November due date and forensic - triage flag add a formal remediation clock. For everyone else, CISA's encouragement to prioritise KEV items is guidance, not a universal statutory deadline.
If auto-updates are off, or a host controls them, check the installed version after updating instead of assuming the change landed. My earlier guide to what WordPress 7.1.4 fixed covers the release itself; this report is about the later CISA exploitation listing.
My website maintenance service includes keeping WordPress core on the current patched release if you want that work handled for you.
About this report
This report is based on official alerts from CISA and the WordPress 7.1.4 release notes on WordPress.org. Facts and quotes are taken from the sources credited below, which I re-read on 6 November 2026. Sections marked "Analysis" are my own view. I am an independent WordPress developer and am not affiliated with the organisations named here.
Credits and sources
- Source: CISA, Cybersecurity and Infrastructure Security Agency, 3 Nov 2026: CISA Adds One Known Exploited Vulnerability to Catalog
- Source: CISA, Known Exploited Vulnerabilities Catalog / CSV, entry dated 2026-11-03: CVE-2026-119977 WordPress Core TOCTOU Race Condition Vulnerability
- Source: Aaron Jorbin, WordPress.org News, 28 Oct 2026: WordPress 7.1.4
- Source: Lance Willett, WordPress.org Documentation / HelpHub, 28 Oct 2026: Version 7.1.4
- Lead image: Illustration created for this article: AI-generated background, with headline text added by Depakar B.
Corrections
Spotted an error? Please contact me. Corrections are noted on this page with the date.