Latest WordPress vulnerability: CVE-2026-119977 #
Update (November 5, 2026): Evidence indicates that this vulnerability is actively exploited in the wild, leading to its addition to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 3, 2026.
WordPress disclosed multiple core vulnerabilities, the most notable being a race condition within its update process. During an update using a complete package, WordPress extracts new files into a predictable, web-accessible directory inside the upgrade folder. An unauthenticated attacker who successfully wins the race during this extraction window can achieve arbitrary code execution on the server. The vulnerability has been designated CVE-2026-119977 and has been rated high with a CVSS score of 8.1.
The following versions are affected
- WordPress 7.1: Versions 7.1.0 through 7.1.3
- WordPress 7.0: Versions 7.0.0 through 7.0.7
- WordPress 6.9: Versions 6.9.0 through 6.9.10
- WordPress 6.8: Versions 6.8.0 through 6.8.11
- WordPress 6.7: Versions 6.7.0 through 6.7.10
- WordPress 6.6: Versions 6.6.0 through 6.6.10
- WordPress 6.5: Versions 6.5.0 through 6.5.13
- WordPress 6.4: Versions 6.4.0 through 6.4.13
- WordPress 6.3: Versions 6.3.0 through 6.3.13
- WordPress 6.2: Versions 6.2.0 through 6.2.14
- WordPress 6.1: Versions 6.1.0 through 6.1.15
- WordPress 6.0: Versions 6.0.0 through 6.0.17
- WordPress 5.9: Versions 5.9.0 through 5.9.19
- WordPress 5.8: Versions 5.8.0 through 5.8.18
- WordPress 5.7: Versions 5.7.0 through 5.7.20
- WordPress 5.6: Versions 5.6.0 through 5.6.22
- WordPress 5.5: Versions 5.5.0 through 5.5.23
- WordPress 5.4: Versions 5.4.0 through 5.4.24
- WordPress 5.3: Versions 5.3.0 through 5.3.26
- WordPress 5.2: Versions 5.2.0 through 5.2.29
- WordPress 5.1: Versions 5.1.0 through 5.1.27
- WordPress 5.0: Versions 5.0.0 through 5.0.30
- WordPress 4.9: Versions 4.9.0 through 4.9.34
- WordPress 4.8: Versions 4.8.0 through 4.8.33
- WordPress 4.7: Versions 4.7.0 through 4.7.38
What is WordPress? #
WordPress is an open source content management system used to build and manage websites, blogs, and web applications.
What is the impact? #
Successful exploitation of this vulnerability would allow an unauthenticated remote attacker to execute arbitrary code on the underlying server during an active core update, resulting in the complete compromise of the hosted web application and all associated data.
Are updates or workarounds available? #
Users are encouraged to update to the latest version as quickly as possible:
- WordPress 7.1: Upgrade to version 7.1.4 or later.
- WordPress 7.0: Upgrade to version 7.0.8 or later.
- WordPress 6.9: Upgrade to version 6.9.11 or later.
- WordPress 6.8: Upgrade to version 6.8.12 or later.
- WordPress 6.7: Upgrade to version 6.7.11 or later.
- WordPress 6.6: Upgrade to version 6.6.11 or later.
- WordPress 6.5: Upgrade to version 6.5.14 or later.
- WordPress 6.4: Upgrade to version 6.4.14 or later.
- WordPress 6.3: Upgrade to version 6.3.14 or later.
- WordPress 6.2: Upgrade to version 6.2.15 or later.
- WordPress 6.1: Upgrade to version 6.1.16 or later.
- WordPress 6.0: Upgrade to version 6.0.18 or later.
- WordPress 5.9: Upgrade to version 5.9.20 or later.
- WordPress 5.8: Upgrade to version 5.8.19 or later.
- WordPress 5.7: Upgrade to version 5.7.21 or later.
- WordPress 5.6: Upgrade to version 5.6.23 or later.
- WordPress 5.5: Upgrade to version 5.5.24 or later.
- WordPress 5.4: Upgrade to version 5.4.25 or later.
- WordPress 5.3: Upgrade to version 5.3.27 or later.
- WordPress 5.2: Upgrade to version 5.2.30 or later.
- WordPress 5.1: Upgrade to version 5.1.28 or later.
- WordPress 5.0: Upgrade to version 5.0.31 or later.
- WordPress 4.9: Upgrade to version 4.9.35 or later.
- WordPress 4.8: Upgrade to version 4.8.34 or later.
- WordPress 4.7: Upgrade to version 4.7.39 or later.
Finding exposed WordPress installations with runZero #
From the Software Inventory, use the following query to locate systems running potentially vulnerable software:
vendor:=WordPress AND product:=WordPress AND version:>0 AND
((version:>=7.1.0 AND version:<7.1.4) OR
(version:>=7.0.0 AND version:<7.0.8) OR
(version:>=6.9.0 AND version:<6.9.11) OR
(version:>=6.8.0 AND version:<6.8.12) OR
(version:>=6.7.0 AND version:<6.7.11) OR
(version:>=6.6.0 AND version:<6.6.11) OR
(version:>=6.5.0 AND version:<6.5.14) OR
(version:>=6.4.0 AND version:<6.4.14) OR
(version:>=6.3.0 AND version:<6.3.14) OR
(version:>=6.2.0 AND version:<6.2.15) OR
(version:>=6.1.0 AND version:<6.1.16) OR
(version:>=6.0.0 AND version:<6.0.18) OR
(version:>=5.9.0 AND version:<5.9.20) OR
(version:>=5.8.0 AND version:<5.8.19) OR
(version:>=5.7.0 AND version:<5.7.21) OR
(version:>=5.6.0 AND version:<5.6.23) OR
(version:>=5.5.0 AND version:<5.5.24) OR
(version:>=5.4.0 AND version:<5.4.25) OR
(version:>=5.3.0 AND version:<5.3.27) OR
(version:>=5.2.0 AND version:<5.2.30) OR
(version:>=5.1.0 AND version:<5.1.28) OR
(version:>=5.0.0 AND version:<5.0.31) OR
(version:>=4.9.0 AND version:<4.9.35) OR
(version:>=4.8.0 AND version:<4.8.34) OR
(version:>=4.7.0 AND version:<4.7.39))
July 2026: CVE-2026-60137 & CVE-2026-63030 #
WordPress disclosed
multiple vulnerabilities affecting the core WordPress framework. The vulnerabilities have been designated CVE-2026-60137 and CVE-2026-63030, and are rated critical with a CVSS score of 9.8. These vulnerabilities have been dubbed wp2shell.
What is the impact? #
Successful exploitation of these issues may allow an unauthenticated remote attacker to conduct an SQL injection and gain remote administrative access and remote code execution on the vulnerable WordPress instances.
Are updates or workarounds available? #
Users are encouraged to update to the latest version as quickly as possible:
- 6.9.5 and later
- 7.0.2 and later
- 7.1 Beta 2 and later
How to find potentially vulnerable systems with runZero #
From the Services Inventory, use the following query to locate potentially impacted assets:
product:"wordpress" AND _service.product:wordpress