Skip to main content
VulnerabilityPublished

CVE-2026-119977: WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution

Affects wordpressSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119977· High 8.1

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

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.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:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 3 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Wordfence

    , 12 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 18 minutes after disclosure

  4. , 3 days after disclosure

  5. 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.

Affected software

ProductAffectedFixed in
Bitnamiwordpresspkg:bitnami/wordpressOther threatsAffected
  • >=4.7.0 <4.7.39
  • >=4.8.0 <4.8.34
  • >=4.9.0 <4.9.35
  • >=5.0.0 <5.0.31
  • >=5.1.0 <5.1.28
  • >=5.2.0 <5.2.30
  • >=5.3.0 <5.3.27
  • >=5.4.0 <5.4.25
  • >=5.5.0 <5.5.24
  • >=5.6.0 <5.6.23
  • >=5.7.0 <5.7.21
  • >=5.8.0 <5.8.19
  • >=5.9.0 <5.9.20
  • >=6.0.0 <6.0.18
  • >=6.1.0 <6.1.16
  • >=6.2.0 <6.2.15
  • >=6.3.0 <6.3.14
  • >=6.4.0 <6.4.14
  • >=6.5.0 <6.5.14
  • >=6.6.0 <6.6.11
  • >=6.7.0 <6.7.11
  • >=6.8.0 <6.8.12
  • >=6.9.0 <6.9.11
  • >=7.0.0 <7.0.8
  • >=7.1.0 <7.1.4
Fixed in
  • 4.7.39
  • 4.8.34
  • 4.9.35
  • 5.0.31
  • 5.1.28
  • 5.2.30
  • 5.3.27
  • 5.4.25
  • 5.5.24
  • 5.6.23
  • 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
  • 6.6.11

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

Community reviews

Loading reviews…