Back to live map

CVE-2026-119977

KEVWordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability

WordPress WordPress Core contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window. This is due to predictable, web-accessible staging paths used during full-package core upgrades.

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
PublishedOct 31, 2026
Last modifiedNov 4, 2026
Added to KEVNov 3, 2026
Remediation dueNov 6, 2026
  • CISA Adds One Known Exploited Vulnerability to Catalog

    CISA has added one new vulnerability to its  Known Exploited Vulnerabilities (KEV) Catalog , based on evidence of active exploitation. CVE-2026-119977 WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise. Binding Operational Directive (BOD) 26-04: Prior

    CISA Alerts · 2d ago
71
Risk assessment · High

Actively exploited. Patch immediately.

Exploitation
Confirmed in the wild (CISA KEV)
Federal remediation deadline
Due today
CVSS
8.1 HIGH
EPSS (30-day exploit probability)
1.2% · top 33% of all CVEs
Weakness
CWE-367
Attack vector
Network, remotely reachable
Preconditions
No privileges and no user interaction
  1. 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  2. 2.Treat as emergency change: patch or isolate internet-facing instances first.
  3. 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
  4. 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.