What happened
WordPress Core 4.7 through 7.1.3 contains a time-of-check time-of-use (TOCTOU) race condition (CWE-367) caused by predictable, web-accessible staging paths used during full-package core upgrades. An unauthenticated attacker can execute code on the server during the upgrade window. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-03 with exploitation status 'active' and a federal due date of 2026-11-06 (CVSS 8.1). Patched in WordPress 7.1.4.
Why it matters
This is the day's sole CISA KEV addition — confirmed in-the-wild exploitation of an unauthenticated RCE. Its AI relevance is indirect but real: a large share of AI applications are delivered as WordPress plugins (AI chat, AI alt-text, AI Engine MCP server, agentic AI plugins) and WordPress MCP/agent endpoints, and they run on this same core. Compromising the core during the upgrade window gives an attacker code execution on the host that also serves those AI surfaces, so any team running AI-on-WordPress must treat the 2026-11-06 KEV due date as urgent and assume-breach.
Attack vector
An unauthenticated attacker races the core upgrade window: predictable, web-accessible staging paths are exposed during a full-package upgrade and an attacker wins the TOCTOU to drop and execute code on the server.
Affected systems
WordPress Core 4.7.0–7.1.3 (any site running AI plugins / AI MCP servers on WordPress).
Mitigation
Upgrade to WordPress 7.1.4+; avoid leaving an upgrade mid-flight and restrict web access to staging paths during upgrades; follow CISA BOD 26-04 (due 2026-11-06) and forensics triage.