Skip to main content
WordPress

CISA says attackers are exploiting a WordPress flaw while sites update

CISA has listed CVE-2026-119977, a WordPress core flaw fixed in 7.1.4 on 28 October, as exploited. It follows wp2shell, the core flaws fixed in July. What to check on your site.

By Published Updated
Illustration: a cartoon robot pressing a large plaster over a cracked website page with a command-line window showing through the crack

Updated, 18 November 2026, 17:37 GMT. WordPress released 7.1.5 on 18 November and says it is a security release that fixes 18 more flaws, four of which need no login. Our 7.1.5 article lists which versions have the fixes. 7.1.4 remains the fix for the upgrade-window flaw, CVE-2026-119977, but 7.1.5 is now the latest release and WordPress.org says to update immediately.

Corrected, 16 November 2026, 18:50 GMT. WordPress released the 7.1.4 fixes for older branches on 28 October, the same day as 7.1.4. On 13 November we wrongly said those backports were still in progress. See Changes at the end.

Updated, 13 November 2026, 14:19 GMT, with a timeline of the security releases and CISA listings since July, and a note to send your host or developer. Earlier today we changed the headline and opening to lead on CISA’s listing of the upgrade-window flaw fixed in 7.1.4, and added that CISA lists the wp2shell flaws as exploited. This article has also been corrected. See Changes at the end.

The US Cybersecurity and Infrastructure Security Agency (CISA) has listed a WordPress core flaw fixed in version 7.1.4 as exploited. It follows wp2shell, the core flaws fixed in July, which CISA also lists. WordPress.org recommends the latest release, which since 18 November is 7.1.5.

Because the flaw is in WordPress itself rather than a plugin, it isn’t limited to sites running a particular add-on.

What to check now

Look at the version in your WordPress dashboard under Updates. It should say 7.1.4 or later. If it doesn’t, or automatic background updates have been switched off on your site, that’s the first thing to sort out. Since 18 November the latest release is 7.1.5, which has fixes for 18 other flaws (our article). Check your plugins are up to date while you’re there. Our free WordPress plugin detector shows what a site is running from the outside.

Still unknown

How widely each of these flaws has been exploited. WordPress.org’s release posts don’t give CVE numbers for most of the other fixes, so it isn’t clear from them which, if any, CISA is tracking.

Changes

Update, 18 November 2026, 17:37 GMT: Added that WordPress 7.1.5 came out on 18 November with fixes for 18 other flaws, with a link to our article on it, to the opening, the timeline, what to check and the note to your host or developer.

Correction, 16 November 2026, 18:50 GMT: Our 11:33 GMT correction on 13 November was wrong about the backports. WordPress.org’s 7.1.4 post said they would ship as they became ready, but they came out the same day: its releases page dates every older-branch version from 4.7.39 to 7.0.8 to 28 October, and the download files we checked, from 7.0.8 to 4.7.39, were published between 16:19 and 21:51 GMT that day.

The first version of this article had that right. We’ve changed the backport paragraph, the timeline, the note to your host and the unknowns.

Update, 13 November 2026, 14:19 GMT: Added a timeline of the security releases and CISA listings since July, with the 21 July listing moved into it, and a note to send your host or developer. Reworded the headline to make clear 7.1.4 fixes the flaw; it was “CISA lists WordPress 7.1.4 upgrade flaw as exploited, after July’s wp2shell”.

Update, 13 November 2026, 11:59 GMT: Changed the headline and opening to lead on CISA’s 3 November listing of CVE-2026-119977, the flaw that made the news most recently, with wp2shell in July as background. The first headline was “wp2shell: the WordPress core flaw from July, and the security releases since”.

Update, 13 November 2026, 11:33 GMT: Added that CISA listed CVE-2026-60137 and CVE-2026-63030 as exploited on 21 July, and the condition CISA gives for CVE-2026-60137.

Correction, 13 November 2026, 11:33 GMT: The first version:

  • said the 7.1.4 fixes were backported to every branch back to 4.7. WordPress.org said the backports were in progress and would ship as they became ready. (This was wrong; see the correction of 16 November above.)
  • said CVE-2026-119977 is being used in real attacks against sites that haven’t updated. CISA’s listing means it has evidence of exploitation; it doesn’t say on what scale or against which sites.
  • said PHP2Shell hit almost every WordPress site. Our evidence is that it affects the PHP that WordPress runs on, not that sites were compromised.
  • included two general statements we couldn’t support with a source, that most WordPress security problems are in plugins and that switching off automatic updates is common. Both are removed.

The upgrade-window flaw

The 7.1.4 post on 28 October lists 12 security fixes, most of them stored cross-site scripting. It also fixes a weakness in the upgrade process that could lead to remote code execution during the upgrade window, and a way for people who aren’t logged in to find unpublished Customizer changes.

That upgrade-window flaw is CVE-2026-119977. WordPress.org’s post gives no CVE number, but CISA’s entry, added to its catalogue on 3 November, links to it. CISA describes it as a race condition in which predictable staging paths during a full core upgrade could let an unauthenticated attacker run code on the server. CISA’s listing means it has evidence of exploitation. It doesn’t say on what scale.

WordPress.org’s 7.1.4 post said the fixes would be backported to every branch still eligible for security fixes, currently back to 4.7, shipping “as they become ready”. They came out the same day. WordPress.org’s releases page dates all 24 older-branch versions, from 4.7.39 to 7.0.8, to 28 October.

WordPress.org also says only the latest version is actively supported.

wp2shell, in July

WordPress 7.0.2 came out on 17 July 2026 and fixed two vulnerabilities, one rated critical and one high. CVE-2026-60137 is a SQL injection issue that applies when a plugin or theme passes untrusted input to WordPress, CISA says. CVE-2026-63030 is a mix-up in how the REST API handles batch requests that, combined with SQL injection, can lead to remote code execution, which could let an attacker run code on the server. Chained together, CISA says, they allow an unauthenticated attacker to do that on default WordPress installations. Wordfence called it the first critical unauthenticated WordPress core remote code execution flaw in nearly a decade, and the pair became known as wp2shell.

WordPress.org’s release post says WordPress 6.9 was affected by both issues and 6.8 by the first one only, with fixes in 6.9.5 and 6.8.6, and versions before 6.8 not affected. It also says the team “enabled forced updates” through the auto-update system for sites on affected versions. The issues were reported by TF1T, dtro and haongo (the SQL injection) and Adam Kues of Assetnote and Searchlight Cyber (the REST API issue).

Timeline

From WordPress.org’s security release posts and CISA’s Known Exploited Vulnerabilities catalogue:

  1. WordPress 7.0.2 fixes the two wp2shell flaws.
  2. CISA lists both wp2shell flaws as exploited.
  3. 6 and 12 Aug 2026Security releases 7.0.3 and 7.0.4.
  4. 17 and 22 Sep 2026Security releases 7.1.1 and 7.1.2.
  5. Security release 7.1.3.
  6. Security release 7.1.4, with the upgrade-window fix, and the same fixes for older branches back to 4.7.
  7. CISA lists the upgrade-window flaw as exploited.
  8. Security release 7.1.5, with 18 further fixes.

PHP2Shell, a separate PHP issue

PHP fixed two critical flaws, known as PHP2Shell, on 21 October. They aren’t WordPress bugs, but WordPress runs on PHP, so the fix needs the host to update the server.

What to ask your host or developer

If your host or a developer looks after WordPress for you, send them this:

Note for your host or developer

Is my WordPress site on 7.1.5, the latest release, or at least 7.1.4?
If it's on an older branch, is it on that branch's 28 October security release, such as 7.0.8 or 6.9.11, or a later one?
Are automatic background updates switched on?
And are the plugins and theme up to date?

Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.