Blog
WordPress Core on KEV: the upgrade-window race, not another plugin headline
CISA added CVE-2026-119977 to KEV on 3 Nov 2026: a WordPress Core TOCTOU race during full-package upgrades via web-accessible staging under wp-content/upgrade/. Operator triage for Core builds, the update window, and forensic cues — without inventing mass compromise.
KEV · Web apps · Operator triage
On 3 Nov 2026, CISA added CVE-2026-119977 to KEV: a TOCTOU race in WordPress Core during full-package core upgrades. Predictable, web-accessible staging under wp-content/upgrade/ can expose installer files (including paths that reach setup-config.php) so an unauthenticated attacker who hits the window can progress to code execution. CISA marks forensic triage required under BOD 26-04; federal due date 6 Nov 2026 (verify catalog).
WordPress shipped the fix in the 7.1.4 security release on 28 Oct 2026 (plus matching security releases on supported older branches). Wordfence’s write-up describes active probing of staged installer paths within hours of the patch — tens of thousands of requests in the first day as scanners wait for sites to update. Treat that as exploitation attempts, not a measured compromise count.
This is Core, not "another plugin KEV." The interesting engagement detail is the upgrade window, not steady-state dashboard auth.
Snapshot
| Field | Value |
|---|---|
| CVE | CVE-2026-119977 |
| Product | WordPress Core |
| Class | TOCTOU race (CWE-367) during full-package core upgrade |
| Auth | Unauthenticated — during the staging window |
| Affected (reported) | 4.7 through 7.1.3 (4.6 and earlier: no security updates — migrate) |
| Fixed (current train) | 7.1.4 (28 Oct 2026); older branches have matching security releases — verify on wordpress.org / your host |
| Precondition | Full-package core update unpacks a predictable, web-reachable tree under wp-content/upgrade/ long enough to abuse |
| Not the whole story | Plugin/theme CVEs are separate; auto-update off / agency-managed fleets are the long tail |
| Scoring tension | WordPress release notes frame the race as one of several security fixes; Wordfence rates the RCE path CVSS 8.1 — do not invent a third score |
| KEV | Added 2026-11-03; forensic triage Yes; due 2026-11-06 (verify) |
Why this shows up mid-engagement
WordPress is common on marketing sites, intranet blogs, and "temporary" campaign hosts that never left the perimeter. On authorized testing:
- Version in the HTML generator meta is useful; whether auto-updates ran through the vulnerable window matters more for hunt
- Blocking
wp-content/upgrade/at the web server is a useful temporary control; putting a deny file *inside* the upgrade folder is fragile on pre-fix code that wipes that directory before unpack - PHP application firewalls that only hook WordPress boot may miss a direct request to a staged PHP file — Wordfence calls out Extended Protection for that reason, and still says firewall ≠ patch
Industry noise says "WordPress RCE." Engagement state asks: which Core build, was a full-package update running, and is upgrade/ web-executable?
Triage questions
- In ROE? WordPress / related hosting authorized?
- Core version? ≥ 7.1.4 or the fixed release for that branch — not "we update plugins weekly."
- Update model? Auto background updates vs manual / host-managed / agency long tail on 4.x–6.x?
- Web access to `wp-content/upgrade/`? Listable or PHP-executable from the internet?
- What do you pause? Unfinished AD/API paths with evidence deserve a clean pause note — do not drop them because Core hit KEV.
Operator path
Loading diagram…
Evidence worth capturing
- Exact Core version string (Dashboard /
version.php/ host panel) before and after remediation - Whether updates are automatic, manual, or host-pushed
- Web-server rules (or lack of them) for
wp-content/upgrade/ - If IR-authorized: access-log hits for
setup-config.phpor other PHP underwp-content/upgrade/around update times; unexpected admin users; unexpected plugins; PHP drops you did not deploy - Do not equate Wordfence’s request counts with confirmed breaches on *this* client
Client-facing remediations (short)
- Update to 7.1.4 or the security release for your branch; confirm the update actually completed
- Before / while updating older builds: deny HTTP access to
wp-content/upgrade/in server/vhost config (filesystem access for WP is enough) - Unsupported 4.6 and earlier: plan a supported upgrade — there is no security train left
- After patching sites that may have updated while vulnerable: hunt the upgrade path and account/plugin anomalies; patch ≠ proof of non-compromise when KEV asks for forensic triage
What not to write
- Treating every WordPress finding as this CVE without a Core version and upgrade-path story
- "Confirmed mass compromise" from scanner request volume alone
- Claiming a plugin firewall replaces the Core update
- Completeness claims ("all WP sites patched") without inventory
- Invented ransomware attribution (KEV ransomware field: Unknown)
Primary sources: CISA KEV alert (3 Nov 2026), WordPress 7.1.4 release notes, and Wordfence 7.1.4 security-release analysis. Re-verify fixed versions on wordpress.org before you file.