RC RANDOM CHAOS

WordPress Vulnerability Opens Final Attack Window During Patching

· via The Hacker News

Original source

Installing the Fix for an Exploited WordPress Flaw Can Expose Some Sites One Last Time

The Hacker News →

A vulnerability in WordPress versions 4.7 through 7.1.3 (CVE-2026-119977) exists during core updates, when the system unpacks the new version into a web-accessible wp-content/upgrade folder using the old, unpatched code. An attacker who determines the folder name can access the installer and execute code before the temporary copy is deleted. WordPress released the fix in version 7.1.4 and matching updates for older branches, but the update process installing the patch creates one final vulnerability window. On versions 5.9 and later, the folder name becomes predictable during this update, enabling attackers to potentially alter the site’s configuration before the patch fully activates.

Wordfence observed attacks beginning nine minutes after deploying a firewall rule. Two sources scanned small groups of sites for approximately 14.5 hours, consistent with attempts to catch the update window. The CVSS score is 8.1 out of 10, though WordPress assigned a lower severity rating. The exploitation window lasted seconds in lab tests.

Sites should block web access to wp-content/upgrade at the server level before updating, or perform manual updates outside the web root. WordPress 4.6 and earlier versions have no security patches and require upgrades to a supported release. After patching, administrators should monitor for unexpected PHP requests to wp-content/upgrade, unrecognized admin accounts, unauthorized plugins, and unfamiliar PHP files in the temporary folder.

Read the full article

Continue reading at The Hacker News →

This is an AI-generated summary. Read the original for the full story.