← All articles

WordPress flaw exploited during core upgrade window

WordPress flaw exploited during core upgrade window

A WordPress flaw that can expose servers during full software upgrades is being actively exploited, according to the U.S. Cybersecurity and Infrastructure Security Agency (CISA). The agency has added the issue to its Known Exploited Vulnerabilities (KEV) catalog, a list of security weaknesses for which there is evidence of real-world attacks rather than only a theoretical risk.

The high-severity vulnerability is tracked as CVE-2026-119977, a standardized identifier used to distinguish a specific publicly disclosed security flaw. It has a Common Vulnerability Scoring System (CVSS) rating of 8.1 out of 10. CVSS is a framework for expressing how serious a vulnerability is based on factors such as how it can be exploited and the potential effect on affected systems. Fixes for CVE-2026-119977 were released late last month.

The weakness is in WordPress Core, the foundational software that runs a WordPress website. CISA classifies it as a time-of-check time-of-use (TOCTOU) race condition. This means the software checks that something is safe, but circumstances can change in the short interval before it uses that item. An attacker who acts within that narrow interval may be able to interfere with the process.

In this case, the opportunity appears during a full-package core upgrade, which replaces the complete set of WordPress Core files rather than applying only a smaller change. CISA said the process uses predictable staging paths, temporary web-accessible locations where upgrade files are prepared. An attacker can target those locations during the upgrade window and potentially achieve arbitrary code execution, meaning the attacker can make the server run commands or software of the attacker’s choice.

The attack does not require authentication, according to Wordfence. In other words, the attacker does not need a username, password or existing account on the website. Exploitation still depends on reaching the vulnerable staged installer path during the brief period when a complete WordPress Core update is under way. That timing requirement narrows the opportunity, but it does not remove the risk for websites running the affected code.

Wordfence reported substantial probing soon after public details became available. During the first 21 hours following disclosure, the WordPress security company recorded more than 18,500 requests aimed at staged setup-config.php installer paths. At the time of its report, Wordfence said it had blocked 12,632 attempts to exploit the flaw during the previous 24 hours. Those measurements describe malicious requests and blocked attempts observed by Wordfence, rather than a count of websites confirmed as compromised.

Separate telemetry, meaning automatically collected technical activity data, came from Previdian. Its honeypot systems, decoy systems designed to attract and record attempted attacks, observed three exploitation attempts on October 30, 2026. Previdian traced the attempts to an Internet Protocol (IP) address, the numerical address used to identify an internet connection, geolocated in the U.K. Geolocation indicates the apparent location associated with the address and does not by itself identify the attacker.

CISA’s confirmation changes the issue from a disclosed vulnerability with observed targeting into one formally recognized by the agency as actively exploited. U.S. Federal Civilian Executive Branch (FCEB) agencies, the civilian federal bodies covered by CISA’s remediation requirements, must apply the available fixes by November 6, 2026. Website owners outside the U.S. federal government are not covered by that deadline, but the exploitation data gives them a clear reason to install the patched WordPress Core software without unnecessary delay.

For website owners reviewing how their sites are run, AEU Hosting offers managed WordPress hosting secured end to end. Regardless of hosting arrangement, administrators should confirm that the available WordPress fix has been applied, because this WordPress flaw can be targeted without an account and specifically becomes exploitable during the core upgrade process.

Also available in: DeutschItalianoShqip