CyberKit

Threat intel / Exploited vulnerabilities

CVE-2026-119977: WordPress core upgrade race leads to remote code execution

A race condition in WordPress core's update process can let an outsider run code on a site during an upgrade. CISA listed it as exploited on 3 November, with a 6 November due date.

High severity. Active. Moderate confidence. First reported 3 Nov 2026, last activity 3 Nov 2026. Briefing updated 11 Nov 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: The WordPress.org release post and the CVE record could not be opened in this refresh, so the fixed version and affected range come from coverage and should be confirmed on WordPress.org. The KEV listing comes from CISA's KEV data feed. Attack-volume counts are left out because outlets disagree.

In plain words

What happened

WordPress runs a large share of the world's websites. A timing flaw in how it installs its own updates can let an outsider run code on the site while an upgrade is under way.

Who is behind it

No group or campaign is named in the coverage checked. CISA's catalog marks ransomware use as unknown.

What they want

Not stated in the sources. Code execution on the web server usually means control of the site and anything it can reach.

What they did

Researchers at Picus reported the flaw. CISA added it to KEV on 3 November as actively exploited.

Who is at risk

Sites running affected WordPress core versions that have not moved to the fixed release.

What to do

  • Update WordPress core to the fixed release named in WordPress's release notes, and confirm the version in the admin dashboard.
  • Check the site for unknown administrator accounts and recently changed PHP files.
  • Take a backup before a manual upgrade, and treat any site that was mid-update during an attack window as possibly compromised.
The technical version, for hunting and patching

What happened

CVE-2026-119977 is a time-of-check to time-of-use race in WordPress core's update process. Per coverage, an unauthenticated attacker can get remote code execution during an upgrade window. Coverage gives CVSS 8.1, but the sources disagree on the affected version range, so no score is given here.

Who is behind it

Reported by Picus researcher Umut Bayram, per coverage. No attribution. Wordfence attack-volume figures differ between outlets, so none is given.

What they want

Not stated. Remote code execution on the web server.

What they did

CISA listed the CVE in KEV on 2026-11-03 with a 2026-11-06 due date, which has passed. Coverage describes the affected range as 4.7.0 through 7.1.3, fixed in 7.1.4.

Who is at risk

WordPress sites running affected core versions, especially sites that upgrade during a busy window or on shared hosts.

What to do

  • Confirm the installed core version, and upgrade to the fixed release named in the WordPress release notes.
  • Review recent admin logins, new users and changed PHP files on any site that was not upgraded.
  • If a site was not upgraded during an update window, treat it as possibly compromised and check it before trusting it.

Vulnerabilities

CVEs in this briefing
CVEProductCVSSCISA KEVFixed in
CVE-2026-119977WordPress coreListed7.1.4 per coverage; confirm on WordPress.org

Sectors: Multiple. Regions: Global.

Open next

Sources

Revision history

  • 2026-11-11: First published.

Newer: ARTEX agents turn exposed GitHub secrets into Azure access in minutes. Older: Fake cracked-software installers push proxyware and adware.