CVE-2026-119977: WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution
Affects wordpressSource GCVE Database
Exploited in the wild · KEV due 6 Nov 2026 · fixed in 6.6.11 : patch wordpress now.
Data as of 17 Nov 2026, 16:05 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 8.1 |
|---|
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
- Patch
- Available – fixed in 6.6.11, 6.5.14, 6.4.14 +17
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 3 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by Wordfence
, 12 hours before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 18 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 3 days after disclosure
KEV remediation due
US federal deadline
, 6 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamiwordpresspkg:bitnami/wordpressOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official patches by upgrading WordPress to one of the fixed versions: 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, or 6.6.11. These versions contain fixes that address the predictable staging path vulnerability. No other mitigation is indicated beyond applying these updates.
Description
WordPress Core versions 4.7.0 through 7.1.3 contain a remote code execution vulnerability due to predictable, web-accessible staging paths during full-package core upgrades. This flaw allows unauthenticated attackers to execute code on the server during the upgrade window. Multiple versions prior to fixed releases are affected. The issue has been addressed in versions 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, and 6.6.11.
References
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php (opens in a new tab)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php (opens in a new tab)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php (opens in a new tab)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php (opens in a new tab)
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php (opens in a new tab)
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-119977 (opens in a new tab)
- wordpress.org/news/2026/10/wordpress-7-1-4/ (opens in a new tab)
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977 (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution (opens in a new tab)