Skip to content
COR Intelligence
Back to The Patch Wave
The Patch WaveAct todayFound by: people

WordPress websites: the update flaw fixed in 7.1.4 is now being used by attackers

COR Solutions6 November 2026
6 min read1,314 words

Wordfence says its firewall has blocked over 240,000 attempts at the WordPress update flaw fixed in 7.1.4 (CVE-2026-119977), which is on CISA's exploited list. Check today that your site is on 7.1.4, or the fix for its older branch.

A hand rests beside an open laptop with a blurred screen among cut flowers and brown wrapping paper on a sunlit workbench in a UK florist's shop.

What happened

WordPress released version 7.1.4 on 28/10/2026 and says it is a security release, so sites should update straight away. WordPress counts 22 problems across 17 advisories, as Patchstack, a WordPress security firm, reports. Most need someone to already have an account on your site. Two do not, and one of those is the serious one: a weakness in the update process itself, which an attacker could use to take over a site during the few seconds an update is running.

Attackers started trying it the same day. On 03/11/2026 CISA, the US cyber security agency, added the flaw (CVE-2026-119977) to its list of security holes attackers are actually using. CISA has not said how many sites were affected. By 05/11/2026 Wordfence said its firewall had blocked over 240,000 attempts, with the busiest day over 74,000 on 30/10/2026.

Does this affect you

Yes, if your business website runs on WordPress and is not yet on 7.1.4 or the fixed version for its branch. WordPress fixed every branch back to 4.7, so a site on 7.0.8, 6.9.11 or 6.8.12, for example, is covered. WordPress 4.6 and earlier no longer get security updates at all, so a site that old needs moving to a current version.

What to do

  1. Log in to your WordPress dashboard and look at the version number at the bottom right of the screen, or in Dashboard, then Updates. You want 7.1.4, or the fixed version for your branch (7.0.8, 6.9.11, 6.8.12 and so on).
  2. If it shows an older number, click Update Now, or ask your web developer or host to update it. WordPress says sites that support automatic background updates will start the update by themselves, but check the number rather than assume it happened.
  3. If someone looks after your site for you, ask them: "Are we on WordPress 7.1.4, or the fix for our branch, and are automatic security updates switched on?"
  4. Once it is updated, ask them to check the wp-content/upgrade/ folder for leftover files, and the lists of plugins and users for anything unexpected, as Wordfence recommends.

Is it being attacked?

Yes. CISA lists it as exploited (03/11/2026). Wordfence saw attempts from 28/10/2026 and by 05/11/2026 had blocked over 240,000. It is still hard to pull off, as Patchstack and Wordfence both point out, because the window is only open while an update runs, and most of the traffic looks like automated probes. A site that is already on 7.1.4, or its branch's fix, is not exposed.

Why it keeps happening: Patchstack says the part of the code behind the update flaw dates back to WordPress 2.8.

If your site may have been broken into

Wordfence's advice, if you find signs of a break-in: remove any unexpected files, plugins and unknown administrator accounts, and check the site for backdoors. In the UK, the NCSC's small business guide says to report a cyber incident to the police through Report Fraud on 0300 123 2040 (or Police Scotland's 101), and some incidents must also be reported to the ICO.

Found by

The update process flaw was reported by Umut Bayram, according to WordPress.org's credits. Other fixes are credited to people at Awesome Motive, VietSunshine Cyber Security, the WordPress Security Team and others, and two to Anthropic. None of the credits say Ai was used. Tag: people.

For developers

  • Release: WordPress 7.1.4, 28/10/2026, short-cycle security release. 7.2 is planned for 08/12/2026 (WordPress.org).
  • Older branches: WordPress.org's post said backports to every branch through 4.7 were "in progress". HelpHub lists them: 7.0 and 6.9 are affected by all 22 issues and fixed in 7.0.8 and 6.9.11; 6.8 by 20 of the 22 (6.8.12); and so on down to 4.7, affected by 2 of the 22 (4.7.39). "WordPress 4.6 and earlier no longer receive security updates." WordPress's version API (checked 07/11/2026) still lists 7.1.4 as latest, with no 7.1.5. Only 7.1.4 is actively supported.
  • Upgrade race condition (Umut Bayram): unauthenticated, but per Patchstack the attacker must request a predictable folder under wp-content/upgrade/ during the seconds an update runs, and that folder must be reachable over the web. Patchstack scored it AC:H. 7.1.4 adds 16 random characters to the folder name, recreates index.php and stops copying wp-config.php out of the working folder. Patchstack's advice: deny web access to wp-content/upgrade/ at the web server and check it is not listable, because a PHP firewall plugin does not run for that request.
  • The update itself: Wordfence notes that "updating from a vulnerable version to the patched version will run the vulnerable upgrade process one last time". As a precaution it suggests blocking access to PHP files in /wp-content/upgrade/ at the web server before updating, but still recommends updating as soon as possible rather than putting it off.
  • Also unauthenticated: unpublished Customizer changesets could be discovered (Antonio Lorensius Silaban).
  • The rest need an account, mostly Contributor or above: stored XSS in block markup, Customizer selective refresh, Categories block, Playlist and image blocks, comments pagination blocks, privacy data removal requests, user logins, and seven Interactivity API advisories (one a browser-tab denial of service).
  • Exploitation attempts (Wordfence, 29/10/2026): first match on its new firewall rule nine minutes after deployment (rule deployed 28/10/2026 20:30 UTC); more than 18,500 requests to staged setup-config.php installer paths in the first 21 hours; two big sources polled small groups of sites for about 14.5 hours. Wordfence: "Not every request used the exact vulnerable path".
  • Wordfence (05/11/2026): over 240,000 blocked exploit attempts since disclosure; highest volume 29/10 to 01/11/2026, peak over 74,000 on 30/10/2026; most requests are automated probes at predictable staging paths. Top sources it lists include 103.59.160.171, 2001:df1:e8c0::106b and 51.89.103.78. Its Free tier gets the rule on 27/11/2026; the exploit hits a PHP file directly, so a firewall plugin needs Extended Protection to see it.
  • After patching, look for unexpected PHP files or requests under wp-content/upgrade, new admin accounts or unknown plugins. Wordfence: "If you find evidence of compromise, we recommend removing any unexpected files, plugins, and unknown administrator accounts, and reviewing the site for backdoors."
  • Bundled root certificates updated because of the eMudhra revocation.
  • CVE-2026-119977 (assigned by Wordfence, published 31/10/2026, CVSS 3.1 8.1, AV:N/AC:H/PR:N/UI:N, CWE-367). Affected 4.7 through 7.1.3; fixed in 7.1.4 and each branch's latest (7.0.8, 6.9.11, 6.8.12 ... 4.7.39). The WordPress.org post itself lists no CVE IDs.
  • CISA KEV: added 03/11/2026, federal due date 06/11/2026, known ransomware use "Unknown" (catalogue 2026.11.06, released 06/11/2026, checked 07/11/2026). Wordfence gives the KEV date as 02/11/2026; CISA's own catalogue says 03/11/2026. Canada's Cyber Centre repeated it in AV26-1117 (03/11/2026). No NCSC alert as of 07/11/2026.

Sources

Read next

More from The Patch Wave