The Hacker News
WordPress update flaw leaves sites exposed during patch installation
Part of the CVE-2026-119977 story · since 3 Nov
- Tue 3 Nov, 20:31 UTC. CISA, first report. CISA Flags Exploited WordPress Flaw Allowing Unauthenticated Code Execution. Cites a CVE in CISA KEV.
- Wed 4 Nov, 08:01 UTC. The Hacker News, its first report on the story. CISA Confirms Active Exploitation of WordPress Core Flaw. Cites a CVE in CISA KEV.
- Wed 4 Nov, 10:31 UTC. Security Affairs, its first report on the story. CISA adds actively exploited WordPress flaw to KEV catalog. Cites a CVE in CISA KEV.
- Fri 6 Nov, 17:30 UTC. The Hacker News. WordPress update flaw leaves sites exposed during patch installation. Cites a CVE in CISA KEV. This article, 4th of 4.
WordPress sites updating a February 2026 vulnerability remain at risk even as the fix lands. Picus Security researcher Umut Bayram says that during the update that installs the patch, WordPress unpacks the new version into a temporary wp-content/upgrade folder using the site’s existing, unpatched code. If an attacker can determine the folder’s name and access the installer before WordPress deletes the copy, they can run code on the server with the web server’s permissions.
CISA added this flaw to its Known Exploited Vulnerabilities catalog earlier in November 2026. The vulnerability is tracked as CVE-2026-119977 and affects WordPress versions 4.7 through 7.1.3. WordPress has issued a fix in version 7.1.4 and backported updates for older branches to 4.7, as listed in its security advisory GHSA-4w3m-c66w-69mg.
Bayram notes that the temporary copy can be created in the upgrade folder even for sites on automatic background updates, and in some update scenarios the attacker may catch the window to craft a malicious wp-config.php within the temporary copy. The fix changes the folder name to a random string, and subsequent updates use the new code paths, but the threat window can persist for sites that still rely on older updater logic.
The Hacker News’ review of WordPress update service shows partial packages are offered within branches like 7.1.3 to 7.1.4, while complete packages are provided for some cross-branch moves; the site’s protection hinges on whether the updater on the affected site has already been patched. Attacks and indicators of compromise include unexpected PHP activity under wp-content/upgrade and unfamiliar administrator accounts, according to Wordfence. The article stresses that the vulnerability’s practical risk depends on the updater state and package contents.
How the story developed
4 articles from 3 outlets since 3 Nov. Quiet since 6 Nov. This was the 4th report, 3 days after the first.
- Tue 3 Nov, 20:31 UTC. CISA, first report. CISA Flags Exploited WordPress Flaw Allowing Unauthenticated Code Execution. Cites a CVE in CISA KEV.
- Wed 4 Nov, 08:01 UTC. The Hacker News, its first report on the story. CISA Confirms Active Exploitation of WordPress Core Flaw. Cites a CVE in CISA KEV.
- Wed 4 Nov, 10:31 UTC. Security Affairs, its first report on the story. CISA adds actively exploited WordPress flaw to KEV catalog. Cites a CVE in CISA KEV.
- Fri 6 Nov, 17:30 UTC. The Hacker News. WordPress update flaw leaves sites exposed during patch installation. Cites a CVE in CISA KEV. This article, 4th of 4.
- Known exploited CVE
- No CVE
- Larger: an outlet’s first report
- Square: official source
- Coverage over time
- Quiet time, folded
Show all 4 articles as a listHide the list
- Tue 3 NovDay 01
- CISA Flags Exploited WordPress Flaw Allowing Unauthenticated Code Execution20:31 · CISA · official · First report · CISA alert · Known exploited CVE
- Wed 4 NovDay 12
- CISA Confirms Active Exploitation of WordPress Core Flaw08:01 · The Hacker News · Known exploited CVE
- CISA adds actively exploited WordPress flaw to KEV catalog10:31 · Security Affairs · Known exploited CVE
Quiet for 2 days
Fri 6 NovDay 31- WordPress update flaw leaves sites exposed during patch installation17:30 · The Hacker News · Picked up again · Known exploited CVE · This article, 4th of 4