Installing the Fix for an Exploited WordPress Flaw Can Expose Some Sites One Last Time
Our summary
Security researcher Umut Bayram of Picus Security has found that applying the fix for an already-exploited WordPress vulnerability, CVE-2026-119977, can momentarily leave sites open to the same attack. The flaw, present in WordPress 4.7 through 7.1.3 and added to CISA's known-exploited-vulnerabilities list this week, lets an unauthenticated attacker who guesses the name of a temporary folder under wp-content/upgrade reach the bundled installer and execute code on the server. WordPress shipped a fix in version 7.1.4, and matching patches for older branches, by randomizing that folder's name — but because the update process itself still runs on the site's old, unpatched code while unpacking the new files, the folder name remains guessable during the very update that installs the fix. Wordfence, which assigned the CVE, reported attack attempts beginning just minutes after it published a firewall rule, with public exploit code already circulating on GitHub; site owners are advised to block web access to wp-content/upgrade before updating, confirm the block returns a 403 error, and then upgrade to 7.1.4 or the corresponding branch release.
The Hacker News publishes this story on its own site; we link to it rather than reprint it.
Worried this affects your company?
Discuss a security assessment of your internet-facing systems. Scope agreed before testing.