An attacker can reach a WordPress core upgrade while its installer files are staged and run code on the server. CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 3. The exposure concerns sites performing a full-package core upgrade with predictable staging paths accessible over the web; the attacker needs no WordPress account.
That is an awkward moment to defend: the server is changing its own code, and a publicly reachable temporary installer gives an outside request a route into that process. CISA calls for vendor mitigations and forensic triage, with a November 6 action date for covered federal agencies. WordPress released 7.1.4 on October 28 to fix this weakness along with other security issues.
Temporary files expose an upgrade
The CVE record, assigned by Wordfence, identifies affected WordPress Core releases from 4.7.0 through 7.1.3 across their respective maintenance branches. It describes predictable, web-accessible staging paths during full-package upgrades. An unauthenticated request that arrives during that window can reach the staged installer and execute code on the server. Researcher Umut Bayram reported the upgrade weakness, according to WordPress’s release announcement.
The exposed staging path becomes reachable during the full-package upgrade, so the update window defines which requests to inspect. Identify where your upgrade workflow stages files, whether the web server can serve that location, and who can reach it while an update runs. Pair the installed-version check with web-server logs from earlier upgrade windows to assess whether staged files were reached.
Confirm fixes on each branch
WordPress says, “Because this is a security release, it is recommended that you update your sites immediately.” Move sites to 7.1.4 where possible and check the installed core version after the update, including on sites configured for automatic background updates. WordPress says security backports to eligible branches through 4.7 were still in progress in its October 28 release announcement. If a site must remain on an older branch, confirm that its installed branch build actually contains the relevant security fix before treating the update as complete.
For upcoming full-package upgrades, restrict public access to the staging location during the change and verify the restriction from an external client before starting the update. Keep the updater’s required local access intact. Record the start and end of each change so web-server requests and file changes can be reviewed against the period when staged installer files were present. These access controls reduce exposure during the upgrade; install the fixed core release as well.
Review the exposed upgrade window
For sites that recently performed a full-package core upgrade on an affected build, preserve web-server access logs for the change window and inspect requests to the staging location alongside unexpected executable files or changes in the site’s web root. If requests reached staged installer content, investigate the host as a possible compromise and follow CISA’s forensic triage direction. CISA lists ransomware-campaign use as “Unknown”; the catalog still marks this vulnerability as exploited.
Verify that the installed core build contains the fix and that an external client cannot reach staging content during the next full-package update. The first check addresses the vulnerable upgrade code; the second tests whether the temporary files remain publicly accessible.