WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability
WordPress — WordPress Core
- Added to KEV catalog
- 3 November 2026
- Federal remediation due date
- 6 November 2026
- Weakness classification (CWE)
- CWE-367
AI Breakdown
What it is
A security flaw in WordPress Core allows unauthenticated attackers to execute unauthorized code on the server during the software upgrade window. This issue occurs because the platform uses predictable, web-accessible staging paths during full-package core updates, creating a time-of-check time-of-use race condition.
Why it matters
Because this flaw is listed on CISA's Known Exploited Vulnerabilities catalog, attackers are actively exploiting it in the wild to compromise servers without needing login credentials. While direct association with known ransomware campaigns is currently unknown, successful exploitation can lead to a complete takeover of the affected web server.
Recommended action
IT teams must immediately apply official vendor mitigations and security updates in accordance with vendor instructions and CISA BOD 26-04 guidelines. Teams should also evaluate all internet-exposed assets, follow forensics triage requirements if compromise is suspected, or discontinue using the product if fixes are unavailable. Federal agencies must complete these required actions by November 6, 2026.
AI-generated from CISA and NVD data — treat as a starting point, not a substitute for your own risk assessment.
CISA Description
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.
Required action
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.
Notes
https://wordpress.org/news/2026/10/wordpress-7-1-4 ; https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-119977
More WordPress Vulnerabilities
WordPress Core Remote File Inclusion Vulnerability
WordPress Core Interpretation Conflict Vulnerability
WordPress Core SQL Injection Vulnerability
WordPress File Manager Plugin Remote Code Execution Vulnerability
WordPress Snap Creek Duplicator Plugin File Download Vulnerability
Is this vulnerability present in your environment?
CRS delivers independent VAPT assessments that identify exactly which known-exploited vulnerabilities exist in your network, applications, and infrastructure.
Explore VAPT Services