WordPress core flaw actively exploited during full-core updates

18.11.2026, Wednesday

CISA added WordPress core flaw CVE-2026-119977 to its Known Exploited Vulnerabilities catalog, citing active exploitation. The attack window is the site's own update process.

On 3 November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-119977, a flaw in WordPress core, to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. What makes this one unusual is where the attack window comes from: the site's own update process.

What the flaw actually does

CVE-2026-119977 is a time-of-check to time-of-use (TOCTOU) race condition in the WordPress core updater. During a full-package core update, WordPress unpacks the new release into a predictable, web-accessible directory under wp-content/upgrade/. According to Wordfence, which published the vulnerability record, an attacker with no account at all can reach the temporarily staged installer files during that brief window and execute PHP code on the server.

The NVD record rates the flaw 8.1 on the CVSS 3.1 scale, in the "high" band. Affected releases run from WordPress 4.7.0 through 7.1.3. The fix shipped with WordPress 7.1.4 on 28 October 2026 and was backported to older branches, including 7.0.8, 6.9.11 and 4.7.39.

Why it matters

In most corporate environments, applying an update is the step that reduces risk. Here the logic inverts: the flaw is only exploitable while an update is running. That puts a particular spotlight on sites with automatic core updates switched on and no one assigned to look after them, because those updates tend to fire at hours when nobody is watching.

The second point is that no authentication is required. An attacker needs no member account, no stolen administrator password and no vulnerable plugin. The third is that proof-of-concept code is already circulating publicly, which means scanning for this is now automated.

What this means for Turkish SMEs

A large share of corporate websites run by small and mid-sized companies in Turkey sit on WordPress, usually on the company's own shared hosting account, alongside contact-form records, job applications and sometimes customer data. For an attacker who can run code on the web server, that means both data and a trusted domain name that can be reused for phishing.

Availability is not the only concern. Under Law No. 6698, a breach affecting a system that holds personal data must be reported to the Personal Data Protection Board, and under the Board's decision no. 2019/10 the window for that notification is 72 hours. A corporate website holding contact-form submissions or a CV pool is not outside the scope of that obligation.

What we recommend at Kamer Bilişim

  • Confirm your core version today. Check the version number on the Updates screen in the admin panel. If you are on 7.1.3 or below, move to the patched release on your own branch (7.1.4, 7.0.8, 6.9.11 or 4.7.39). Run the update at a controlled time, with a backup taken and, where possible, the site in maintenance mode.
  • Close off the upgrade directory. In your server configuration, block direct web access to wp-content/upgrade/. That shuts the path used in this attack and makes future attempts built on the same logic harder.
  • Give the update process an owner. Keep an inventory listing which version runs on which site, store a daily backup in a location separate from the server, and make patch tracking a standing maintenance item. Once you pass a handful of sites, tracking this by hand stops working in practice.

Kamer Bilişim has provided hosting, server maintenance and patch management to corporate clients across the Anatolian side of Istanbul since 2006. To go through which versions your sites are running and whether their upgrade directories are exposed, you can reach us through our contact page.

Source: CISA – Known Exploited Vulnerabilities Catalog (3 November 2026), Wordfence and NVD vulnerability records.

Source: CISA

Message us on WhatsApp