CISA adds the WordPress core upgrade-window flaw to its list of actively exploited vulnerabilities
The US cybersecurity agency CISA added WordPress core flaw CVE-2026-119977 to the Known Exploited Vulnerabilities (KEV) catalog, dated November 3, 2026. The fix shipped in 7.1.4 on October 28, and federal agencies have until November 6 to act.
CISA put the flaw into the KEV catalog on November 3
CISA's KEV entry describes CVE-2026-119977 as a time-of-check to time-of-use (TOCTOU) race condition in WordPress core. It lists November 3, 2026 as the date added and November 6, 2026 as the due date. BleepingComputer's November 4 report says CISA confirmed active exploitation on Tuesday and ordered federal civilian agencies to secure their systems by Friday under BOD 26-04.
The fix itself is not new. The WordPress team shipped the 7.1.4 security release on October 28, and we are not retelling that release, which we covered on October 29. The news here is that the flaw is now officially on the list of actively exploited vulnerabilities.
Predictable staging paths open a door to code execution on the server
According to CISA's description, the root cause is that full-package core upgrades stage files in locations that are easy to guess and can be reached over the web. An unauthenticated attacker could run code on the server while the upgrade window is open. The entry marks forensic triage as Yes and shows an Unknown value for use in ransomware campaigns.
The Hacker News reported on October 30, when the flaw had no CVE yet, that it carries a CVSS score of 8.1 and affects WordPress core from 4.7 through 7.1.3. Its write-up says the affected versions extract full-package updates to an easy-to-guess folder inside wp-content/upgrade, and that copy includes the WordPress installer. The WordPress.org announcement lists a fix for a weakness that could allow remote code execution during the upgrade window and credits Umut Bayram. The fixes are being backported to every branch that receives security fixes, currently back to 4.7, and ship as each is ready.
Attack counts measure different time windows
Each outlet passes along Wordfence figures for a different time window. The Hacker News (October 30) cites 62,969 blocked attacks in 24 hours. BleepingComputer (November 4) cites a weekend Wordfence advisory update saying it blocked 13,095 attacks in the past 24 hours. SecurityWeek reports more than 18,500 requests aimed at staged setup-config.php installer paths in the first 21 hours, with no successful compromises reported, and quotes Wordfence: "The first match for our new firewall rule arrived nine minutes after deployment." Because the windows differ, these numbers should not be added together or compared one to one. SecurityWeek's November 4 update also says the CVE identifier has now been assigned and that federal agencies got a three-day deadline.
BleepingComputer and SecurityWeek call the flaw high severity; the CVSS 8.1 score and the 4.7 to 7.1.3 version range come from The Hacker News, so we attribute those values to that outlet. The practical point is clear: because the upgrade window itself is the attack surface, WordPress sites with automatic updates off or delayed are directly exposed. The WordPress team says it is "recommended that you update your sites immediately". The Hacker News suggests moving to 7.1.4 (per WordPress.org, backported releases for older branches ship as they become ready), checking for suspicious requests to PHP files under wp-content/upgrade, and looking for administrator accounts, plugins or PHP files you do not recognize.
The sources do not mention Türkiye, so this section is UNALSOFT's take
The CISA entry, the WordPress.org announcement and the three news reports contain no information about Türkiye: no figures on affected sites there, no statement from a local authority and no Türkiye-specific date. This section is therefore not a fact drawn from the sources. It is UNALSOFT's own commentary.
Our view: from what we observe, WordPress is widespread among small and mid-sized business sites in Türkiye, and updates can easily be postponed. When the update window itself is the attack surface, that habit becomes riskier. From these sources we cannot tell how many sites in Türkiye are affected, whether any attack came from our region, or whether a local authority has issued a warning.
UNALSOFT's take
We read this story as a maintenance reminder. The order is simple: find the site's WordPress version, check whether automatic background updates are on, take a backup before updating, then review administrator accounts and the upgrade folder. As an agency we include this in post-launch maintenance on our web design projects; because the story is limited to what the sources say, it does not suggest a local legal or technical conclusion.
Sources
CISA KEV catalog (JSON feed) · WordPress.org News · BleepingComputer · SecurityWeek · The Hacker News
Is your WordPress site on 7.1.4 or a backported release?
A short call is enough to check your version, your automatic update setting and your administrator accounts together.