WordPress CVE-2026-119977: Patch Update Flaw

The WordPress core update flaw hinges on an HTTP-reachable temporary installation, not just an outdated version. Here’s the patch and the checks that matter.

CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 3, confirming active exploitation. WordPress released version 7.1.4 on October 28 with a fix, alongside fixes for supported older branches. Wordfence reported blocking 13,095 attack attempts in a 24-hour period. Those were attempts, not confirmed victims or compromises.

How CVE-2026-119977 affects the WordPress update process

The flaw concerns WordPress’s core update process. A researcher’s analysis says an attacker may be able to reach a temporary installation created during an update and use it to execute code on the server. That path depends on specific conditions, including the temporary files being reachable over HTTP. A vulnerable version alone does not prove that a site was exposed or compromised.

Before updating, deny web access to /wp-content/upgrade/ and confirm that the rule works. Our WAF protection can add another layer if configured with a specific, tested rule for this path. Verify that it blocks the relevant requests and that traffic cannot bypass the WAF. This is supplemental protection, not a substitute for directory access controls or installing the security fix.

Patch WordPress, then check what changed

  • Update to WordPress 7.1.4 or the fixed security release for your branch. If your site runs an unsupported version, move it to a supported release.
  • Review web server and WordPress logs for unexpected requests to upgrade or setup paths, especially around recent update activity.
  • Check for unfamiliar files, administrator accounts, or changes to site content. If anything looks wrong, investigate rather than assuming that patching resolved it.

WordPress has published the 7.1.4 security release details. For the technical conditions and update-window mitigation, see the researcher’s analysis and BleepingComputer’s report.

If you’re unsure whether your WordPress site is exposed or properly protected, a quick review can help clarify the next step.


Book a 15-minute website security check
We’ll review your setup and explain what needs attention, with no obligation.