
The US Cybersecurity and Infrastructure Security Agency (CISA) added a high-severity WordPress Core flaw to its Known Exploited Vulnerabilities (KEV) catalog on Nov. 3, after attackers began exploiting it. The vulnerability affects the WordPress upgrade process and could let an unauthenticated attacker run code on a server during an update, according to BleepingComputer and the SC Media report.
What happened
The flaw is tracked as CVE-2026-119977. SC Media reports a CVSS severity score of 8.1. It is a time-of-check time-of-use (TOCTOU) race condition in full-package WordPress Core upgrades: new files are extracted into a predictable, web-accessible staging directory, and an attacker who reaches the files before they are moved or removed may be able to invoke PHP code with the web server’s privileges.
BleepingComputer reports that CISA confirmed exploitation on Tuesday and added the flaw to the KEV catalog on Nov. 3. The WordPress security team released WordPress 7.1.4 on Oct. 28 to address the issue and recommended updating sites immediately. BleepingComputer also reports that Wordfence said it blocked 13,095 attacks targeting the flaw in the past 24 hours, in an advisory update over the weekend.
Why this matters to small businesses
A restaurant, café, salon, spa, plumbing business or electrician may be affected if its website runs WordPress and is exposed to the vulnerable upgrade path. The reports do not establish that every WordPress site has been compromised, or that every small business faces the same requirements. CISA’s binding deadline applies to US Federal Civilian Executive Branch agencies; BleepingComputer says CISA also urged network defenders in the private sector to prioritize patching.
For a business site, a compromise can matter beyond the visible pages. Keeper Security’s chief information security officer, Shane Barney, said web servers can sit beside production databases, service accounts and API keys, which attackers may seek to reach after gaining a foothold.
Background and context
The WordPress security team described the issue on Oct. 28 as “A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window.” SC Media says the underlying patch was released that day; it also reports the flaw was publicly disclosed and published on Oct. 31, while the CVE record lists Oct. 28 as its disclosure date.
The risk is tied to the update process itself, including automatic updates, rather than only to a website’s normal public pages. SC Media reports that exposed sites may be targeted while an update is in progress, even though the opportunity may be brief.
What to check next
SC Media recommends blocking external web requests to PHP files under /wp-content/upgrade before upgrading, then checking for requests to PHP files in upgrade directories, especially requests followed by unexpected PHP processes or outbound connections. Its additional checks include looking for unauthorized administrator accounts, unfamiliar plugins, unexpected PHP files and changes to wp-config.php. If a compromise is suspected, Barney advises rotating database passwords, API keys and service credentials stored on or accessible to the web server.
BleepingComputer reports that federal agencies were ordered to secure their systems by Friday under Binding Operational Directive 26-04. That deadline is for those agencies; private businesses should confirm their own remediation with their website maintainer.
Source: bleepingcomputer.com