Last week we wrote about WordPress 7.1.4 and its strangest fix: a weakness in the update process itself. At the time, WordPress had not published the details, and we said we would not guess at them.
Two things have happened since. On November 3, the Cybersecurity and Infrastructure Security Agency added the flaw, CVE-2026-119977, to its catalog of vulnerabilities known to be exploited. And the researcher who found it has published how it works, including a step that most update instructions leave out.
Where this comes from. The WordPress 7.1.4 release post and WordPress's security advisory for the flaw, the CVE record including CISA's entry, the write-up by the researcher at Picus Security who reported it (updated November 9), and Patchstack's analysis, all read directly.
How the Attack Works
When WordPress updates itself, it unpacks the new version into a folder under wp-content/upgrade, then copies the files into place. On most versions, that folder's name is predictable, and the installer inside it can be reached from the web without logging in.
During the seconds the files sit there, an attacker can use that installer to replace the site's configuration so it points at a database the attacker controls, then create an administrator account. From there, they can upload code.
The CVE record lists WordPress 4.7 through 7.1.3 as affected. And because the update to 7.1.4 is carried out by the old, unpatched updater, the researcher notes that the first update itself is exposed.
Why the Severity Ratings Disagree
WordPress's own advisory rates the flaw low. The CVE record scores it 8.1, high. Patchstack, which sells WordPress security, rates the attack as hard to pull off and says it would not call it practical to exploit. CISA says it is being exploited.
When CISA says a flaw is being exploited, that settles the question of whether to act. The catalog is the list federal agencies are required to patch against, and CISA urges every organization to use it to set priorities. Cities, counties, school districts and businesses that follow it should treat this one as due now.
The Step to Take Before You Update
The researcher's advice is to block web access to the staging folder before updating, so the installer cannot be reached during the window:
- Block the folder at the web server. Deny web requests to /wp-content/upgrade/ in the server configuration for Nginx or Apache, or with a rule in the site's main .htaccess file.
- Confirm it is blocked. Request a URL inside /wp-content/upgrade/ in a browser. It should return 403, Forbidden. Do not update until it does.
- Do not put the rule inside the folder. The old updater deletes that folder before unpacking, so a rule placed inside it disappears exactly when it is needed.
- The command line is not a shortcut. The researcher says running the update from the command line with WP-CLI is not a substitute, because it uses the same unpacking step.
Patchstack adds a point we made about PHP2Shell last month: a security plugin cannot block this. It runs inside WordPress, and the attack happens in files WordPress has not loaded. The block has to be at the web server.
If You Are on a Managed Host
On platforms that control core updates, such as Pantheon or WP Engine, you may not run the update yourself. Ask your host two questions in writing: is /wp-content/upgrade/ reachable from the web on our site, and which WordPress version is each environment running right now?
After You Update
Neither the researcher nor Patchstack published a checklist for finding an earlier compromise. Based on how the attack works, these are the places we would look:
- The version. Confirm the dashboard shows 7.1.4, or the latest backport for your branch, on every copy of the site.
- The configuration file. Check that the database settings in wp-config.php still point at your own database.
- Users and plugins. Look for administrator accounts and plugins nobody recognizes.
- The staging folder. Look for leftover files under wp-content/upgrade/ that should not be there.
Have Us Update Your WordPress Site Safely
We block web access to the upgrade folder, confirm it returns Forbidden, update every copy of your site to 7.1.4 or the right backport, and check the configuration, users and plugins afterward. If you want this handled for every release, our partnership plans include security patching.