No. CVE-2026-119977
Hackers can take over WordPress sites while they update
Yes. Attackers are using this right now.
Anyone running a WordPress website, including small business and personal sites.
What to do
Update WordPress to the latest version, or ask your web host to do it, and avoid leaving updates half-finished.
- Confirmed in attacks
- Nov 3, 2026
- Product
- WordPress Core
- Attack likelihood, next 30 days
- under 1%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official 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.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is WordPress WordPress Core (CVE-2026-119977) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-119977. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.