Installing the Fix for an Exploited WordPress Flaw Can Expose Some Sites One Last Time
What happened
WordPress released fixes for actively exploited CVE-2026-119977 in version 7.1.4 and supported older branches, but researcher Umut Bayram warns that some sites remain exposed while installing the patch. On affected sites running 5.9 or later, the old updater still creates a predictable, web-accessible temporary folder; if the package includes installer files, an unauthenticated attacker who reaches them before deletion can run PHP with the web server’s permissions. Bayram recommends blocking web access to wp-content/upgrade before updating, because the patch-installation process still uses the vulnerable unpacking code.
Why it ranks #1
WordPress patched actively exploited CVE-2026-119977, but some sites remain exposed during installation because the old updater can leave installer files web-accessible, allowing unauthenticated PHP execution.
Who should care
CISOs and security leaders, SOC and incident response teams
- Impact
- moderate
- Urgency
- near-term
- Confidence
- high
- Scope
- enterprise
- Status
- actively exploited