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

Exploited in the wild High 8.1 EPSS 0.6% WordPress core

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

CVE-2026-119977CVE identifier
8.1CVSS 3.1 base score (high)
2026-11-03added to CISA's exploited list (US federal deadline 2026-11-06)
0.6%EPSS: chance of exploitation in the next 30 days (higher than 49% of CVEs)
2026-10-31published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run WordPress core and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Nothing to restart; most installs update core themselves (wp core update with WP-CLI); reload PHP-FPM to flush OPcache
Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

WordPress Foundation WordPress 4.7.0 to 4.7.38
WordPress Foundation WordPress 4.8.0 to 4.8.33
WordPress Foundation WordPress 4.9.0 to 4.9.34
WordPress Foundation WordPress 5.0.0 to 5.0.30
WordPress Foundation WordPress 5.1.0 to 5.1.27
WordPress Foundation WordPress 5.2.0 to 5.2.29
WordPress Foundation WordPress 5.3.0 to 5.3.26
WordPress Foundation WordPress 5.4.0 to 5.4.24
WordPress Foundation WordPress 5.5.0 to 5.5.23
WordPress Foundation WordPress 5.6.0 to 5.6.22
WordPress Foundation WordPress 5.7.0 to 5.7.20
WordPress Foundation WordPress 5.8.0 to 5.8.18

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian

sudo apt update
sudo apt install --only-upgrade wordpress

Ubuntu

sudo apt update
sudo apt install --only-upgrade wordpress

RHEL, AlmaLinux, Rocky, Oracle

sudo dnf upgrade --refresh wordpress (EPEL)

Fedora

sudo dnf upgrade --refresh wordpress

SUSE / openSUSE

not packaged

Amazon Linux

not packaged: upstream

Arch Linux

sudo pacman -Syu

Alpine

not packaged

FreeBSD

pkg update && pkg upgrade wordpress

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

https://wordpress.org/news/2026/10/wordpress-7-1-4 ; https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-119977

Sources

Page generated automatically from official sources on 2026-11-04 06:29 UTC. Always confirm with your vendor's advisory.