•

WordPress upgrade flaw exploited: what site owners should do now

Cybersecurity specialist checks a vulnerable WordPress website on laptop

Attackers are targeting a high-severity flaw in WordPress Core that can enable remote code execution during a site upgrade. CISA has added the vulnerability to its Known Exploited Vulnerabilities catalog, urging organisations to act quickly. WordPress has released fixes, but researchers warn that installing an update can leave a brief window of risk on some sites.

Key takeaways

CVE-2026-119977 affects WordPress 4.7 through 7.1.3 and has a CVSS score of 8.1. The weakness is in the core upgrade process, not a plugin or theme, and attackers do not need a site account to attempt exploitation.

  • Update to WordPress 7.1.4 or a fixed release for your branch.
  • Before updating, block public web access to wp-content/upgrade where possible.
  • Check logs and site files for signs of unauthorised access, particularly if your site was exposed during an update.

Why CISA is warning site owners

The flaw, tracked as CVE-2026-119977, is a time-of-check-to-time-of-use race condition. During some full-package updates, WordPress temporarily places installation files in a location that may be accessible over the web. An attacker repeatedly probing for that temporary installer could reach it during the short period before the files are removed and potentially run code on the server.

CISA says it has evidence of active exploitation and set a 6 November 2026 remediation deadline for US federal civilian agencies. The warning is relevant well beyond government: Wordfence reported more than 18,500 requests targeting staged installer paths in the first 21 hours after disclosure. These were attempts, not proof that every targeted site was compromised.

Updating needs care as well as urgency

WordPress 7.1.4, released on 28 October 2026, addresses the vulnerability, with fixes also made available for eligible older branches. However, security researcher Umut Bayram warned that some sites may still use vulnerable updater code while installing the fix. Blocking web access to the upgrade directory before updating can reduce this exposure; server configuration should be checked to confirm requests are denied.

Sites that cannot safely restrict access can consider a manual update performed outside the web server’s public directory. Administrators should follow WordPress guidance and back up files and the database before making changes. Older WordPress 4.6 and earlier releases no longer receive security updates and should be moved to a supported version.

What to check after patching

A completed update does not establish whether a site was accessed during an earlier upgrade window. Review web logs around update times for unusual requests to wp-content/upgrade or staged setup-config.php files. Also look for unfamiliar administrator accounts, unexpected plugins, PHP files, configuration changes or unusual server activity.

A WordPress maintenance plan can help make these checks routine through update management, backups and ongoing site monitoring. For site owners without time to manage security tasks themselves, a WordPress care plan can provide a structured way to keep updates and basic security reviews from being overlooked. If you suspect compromise, preserve relevant logs and investigate before treating the patch as the only necessary step.