Exploited in the wild

CVE-2026-119977: WordPress Core Upgrade-Window RCE (Exploited)

Inttelio Threat Feeds ·

CVE-2026-119977 is a time-of-check time-of-use (TOCTOU) race condition in WordPress Core versions 4.7 through 7.1.3. During full-package core upgrades, WordPress uses predictable, web-accessible staging paths, which lets unauthenticated attackers execute code on the server while the upgrade is running. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on November 3, 2026, so it is confirmed exploited in the wild.

CVECVE-2026-119977
Vendor / productWordPress WordPress Core
CVSS v3.18.1 HIGH
WeaknessCWE-367
Exploited in the wildYes - added to CISA KEV November 3, 2026
CISA due date (federal agencies)November 6, 2026
PublishedOctober 31, 2026

Who is affected

Any organization running WordPress Core versions 4.7 through 7.1.3, as stated in the NVD description. The exposure occurs during full-package core upgrades, so sites that are being upgraded, or that upgrade automatically, are at risk during that window. The source data references the WordPress 7.1.4 release announcement (https://wordpress.org/news/2026/10/wordpress-7-1-4/). It does not explicitly state the fixed version or whether fixes were backported to older branches. Confirm the fixed versions in the vendor and Wordfence advisories.

What attackers can do

An unauthenticated attacker with network access to the site can race the upgrade process. They target the predictable staging paths used during a full-package core upgrade to execute code on the web server. Successful exploitation means full compromise of confidentiality, integrity, and availability (CVSS 3.1 base score 8.1, High). Attack complexity is rated High because the attacker has to hit the upgrade window. No login and no user interaction are required. The source data does not include indicators of compromise, attacker identities, or exploitation techniques beyond this description.

Exploitation status

Exploited in the wild. CISA added CVE-2026-119977 to the KEV catalog on 2026-11-03 with a due date of 2026-11-06. That due date binds U.S. federal civilian agencies under BOD 26-04. Other organizations, including contractors and private companies, should treat the short three-day deadline as a signal of urgency. CISA flags the entry for forensic triage. Known ransomware campaign use is listed as Unknown.

What to do now

  1. Inventory every WordPress site you own or that is hosted for you, including marketing sites, staging environments, and sites run by agencies or managed hosts. Record each site's Core version.
  2. Identify every site running WordPress Core 4.7 through 7.1.3 and treat it as affected.
  3. Read the vendor release notes (https://wordpress.org/news/2026/10/wordpress-7-1-4/) and the Wordfence advisory to confirm the fixed version for your branch. Also check whether either source gives guidance on performing the upgrade safely. The vulnerability is triggered during the upgrade window itself, and the source data does not state specific mitigations for that window.
  4. Apply the vendor fix following vendor instructions, prioritizing internet-facing sites. If you cannot apply the fix or vendor mitigations, consider taking the site offline until you can. This mirrors the KEV instruction to discontinue use if mitigations are unavailable.
  5. Check for compromise, especially on sites that ran a core upgrade while on a vulnerable version. Look for unexpected files in the web root and upgrade/staging directories, unfamiliar PHP files, new administrator accounts, and unusual outbound connections or web server processes. The source data provides no indicators of compromise, so use your web server logs and file integrity baselines. CISA has flagged this entry for forensic triage; see the BOD 26-04 Forensics Triage Requirements guidance linked in the KEV notes.
  6. If you find signs of compromise, preserve logs and disk images before you clean up, rotate credentials stored on the server (database, API keys, admin passwords), and rebuild from a known-good source.
  7. Federal contractors and agencies' service providers should confirm with customers whether BOD 26-04 requirements apply to systems they operate on an agency's behalf.

Frequently asked questions

Which WordPress versions are affected by CVE-2026-119977?

WordPress Core versions 4.7 through 7.1.3 are affected, according to the NVD description. The references point to the WordPress 7.1.4 release announcement. The source data does not explicitly confirm the fixed version for each branch, so check the vendor advisory.

Is CVE-2026-119977 being actively exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on November 3, 2026, with a due date of November 6, 2026 for U.S. federal civilian agencies. Whether it has been used in ransomware campaigns is listed as Unknown.

Does an attacker need a WordPress login to exploit CVE-2026-119977?

No. The flaw can be exploited by unauthenticated attackers over the network with no user interaction. The attacker does have to time the attack to the window when a full-package core upgrade is running, which is why the attack complexity is rated High.

Sources

This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.

Not sure if you are exposed?

Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.

Talk to Inttelio