WordPress · WordPress Core · CWE-367 · published 2026-10-31
CVE-2026-119977WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability
Patch today Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
CVE-2026-119977 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-03. EPSS estimates a 1.6% chance of exploitation in the next 30 days, higher than 76% of all CVEs. This WordPress Core vulnerability: CVSS 8.1 (v3.1), a successful attack gives total control of the component. Patched packages are out for Debian; Debian still has unfixed releases. US federal agencies must remediate by 2026-11-06. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA 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. (federal due date 2026-11-06)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | wordpress | Fixed in 6.8.12+dfsg1-0+deb13u1 |
| 12 bookworm | wordpress | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web applicationWordPress Core
Time-of-check Time-of-use (TOCTOU) Race ConditionCVE-2026-119977
Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-11-03 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 1.6% (76th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.1 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
More from this vendor: all WordPress vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- WordPress Foundation WordPress
4.7.0through4.7.38(affected)4.8.0through4.8.33(affected)4.9.0through4.9.34(affected)5.0.0through5.0.30(affected)5.1.0through5.1.27(affected)5.2.0through5.2.29(affected)5.3.0through5.3.26(affected)5.4.0through5.4.24(affected)5.5.0through5.5.23(affected)5.6.0through5.6.22(affected)5.7.0through5.7.20(affected)5.8.0through5.8.18(affected)5.9.0through5.9.19(affected)6.0.0through6.0.17(affected)6.1.0through6.1.15(affected)6.2.0through6.2.14(affected)6.3.0through6.3.13(affected)6.4.0through6.4.13(affected)6.5.0through6.5.13(affected)6.6.0through6.6.10(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.