Skip to content

CVE-2026-119977: WordPress Core Predictable Staging Path Remote Code Execution

Density:
C-Level Executive Briefing CVE-2026-119977 CRITICAL SCORE 96/100

On November 3, 2026, CISA cataloged CVE-2026-119977 in the Known Exploited Vulnerabilities (KEV) catalog with a mandatory remediation deadline of November 6, 2026. The vulnerability affects WordPress Core versions 4.7 through 7.1.3. During background updates of core components, themes, and translation packs, WordPress temporarily unpacks assets into predictable, web-accessible directories within wp-content/upgrade/. Automated cybercrime botnets and opportunistic threat actors actively race the extraction thread to execute newly dropped PHP files before cleanup, achieving instant server compromise. Immediate patching to WordPress 7.1.4 (or respective maintenance branches) and blocking web access to wp-content/upgrade/ is mandatory.

HYBRID

HERMES THREAT SCORE & CMS ECOSYSTEM RISK ANALYSIS

Target: WordPress Core Automatic Update Subsystem & File Extraction Engine
Confidence: 99%
96 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 20 / 20
Prevalence 20 / 20
Impact 19 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20

On October 31, 2026, WordPress released security maintenance releases addressing CVE-2026-119977. The flaw affects WordPress Core versions from 4.7 through 7.1.3, representing millions of deployed production websites worldwide.

By exploiting deterministic naming conventions in temporary directories created during update extraction (wp-content/upgrade/), an attacker can predict file locations and trigger code execution during the transition window before archive verification and cleanup occur.

When the WordPress Core_Upgrader or Plugin_Upgrader downloads and decompresses ZIP packages, it extracts payload files into:

/wp-content/upgrade/[package_hash]_[timestamp]/

Because the package hash is derived from static metadata and timestamps can be approximated through server response headers, the temporary extraction path is predictable. If web servers do not explicitly block direct HTTP access to /wp-content/upgrade/, an attacker can request the newly extracted PHP entrypoint before WordPress finalizes the installation and removes the temporary files.

Threat Intelligence & Observed Indicators of Compromise (IOCs)

Section titled โ€œThreat Intelligence & Observed Indicators of Compromise (IOCs)โ€
Indicator TypeObservable / IndicatorRole / AttributionStatusSource
IPv4 Address185.196.220[.]84Automated staging race-condition probe nodeACTIVECrowdSec CTI
IPv4 Address194.26.29[.]112Malicious payload staging & webshell deploymentACTIVEShadowserver
IPv4 Address45.154.255[.]89Distributed WordPress crawler & brute-forcerACTIVEGreyNoise
IPv4 Address91.240.118[.]172Secondary C2 listener for injected PHP stagersACTIVEVulnCheck
File SHA-256b8c45d3e21a7894f6c5b019842a8e7f123456789abcdef0123456789abcdef01wplogin_cache.php (Secondary stage backdoor dropper)CONFIRMEDHermes Telemetry
File SHA-256a1e2f3d4c5b6a7890123456789abcdef0123456789abcdef0123456789abcdefwp-atom.php (Obfuscated persistent webshell)CONFIRMEDHermes Telemetry
URI Pattern/wp-content/upgrade/tmp_upg_*/wp-login.phpExploitation probe patternACTIVEWeb Application Firewall
URI Pattern/wp-content/upgrade/*/wplogin_cache.phpPost-exploitation backdoor access attemptACTIVESOC Telemetry
alert http any any -> $HTTP_SERVERS any (
msg:"ET EXPLOIT WordPress Core Staging Path RCE Probe (CVE-2026-119977)";
flow:established,to_server;
http.uri; content:"/wp-content/upgrade/"; nocase;
pcre:"/\/wp-content\/upgrade\/[^\/]+\.php/i";
classtype:web-application-attack;
sid:202611997;
rev:1;
)

The WordPress Core security team remediated this vulnerability via Trac Changeset 59382. The patch fundamentally revamps wp-admin/includes/class-wp-upgrader.php and wp-admin/includes/file.php:

  • Replaces deterministic package timestamps with 32-character cryptographically secure pseudo-random hashes (wp_generate_password(32, false)).
  • Dynamically creates temporary .htaccess and web.config files inside the staging directory that immediately deny all HTTP execution of .php, .phtml, and .php7 scripts.
  • Verifies directory ownership and write privileges using atomic lock-files prior to decompressing update archives.
Major BranchVulnerable VersionsFixed ReleasePatch Commit Reference
WordPress 7.17.1.0 โ€“ 7.1.37.1.4Changeset 59382
WordPress 7.07.0.0 โ€“ 7.0.57.0.6Backported Maintenance Branch
WordPress 6.96.9.0 โ€“ 6.9.76.9.8Backported Maintenance Branch
WordPress 6.86.8.0 โ€“ 6.8.36.8.4Backported Maintenance Branch
WordPress 6.76.7.0 โ€“ 6.7.16.7.2Backported Maintenance Branch
WordPress 6.66.6.0 โ€“ 6.6.26.6.3Backported Maintenance Branch
WordPress 6.56.5.0 โ€“ 6.5.56.5.6Backported Maintenance Branch
WordPress 6.46.4.0 โ€“ 6.4.46.4.5Backported Maintenance Branch
  1. Apply Vendor Security Updates: Upgrade WordPress installations across all branches immediately using WP-CLI or the dashboard:
    Terminal window
    wp core update --version=7.1.4
  2. Web Server Hardening (Immediate Virtual Patch): Add web server rules (NGINX / Apache .htaccess) to deny direct execution of PHP files inside the wp-content/upgrade/ directory:
    location ~* /wp-content/upgrade/.*\.php$ {
    deny all;
    return 403;
    }
  3. Audit File Integrity & Eliminate Droppers: Verify core file checksums and scan for unauthorized .php files in wp-content/upgrade/:
    Terminal window
    wp core verify-checksums
    find /var/www/html/wp-content/upgrade/ -type f -name "*.php" -delete
๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-119977: WordPress Core Predictable Staging Path Remote Code ExecutionVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTMicrosoft Office & 365 Apps
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”

Supporting Verified Evidence: