Skip to content
PiLabs security advisory Updated 17 November 2026
High 8.1 CVE-2026-119977 Known exploited

Remote code execution during core upgrades in WordPress Core

Affected
WordPress Core
Affected versions
≥ 4.7, < 4.7.39; ≥ 4.8, < 4.8.34; ≥ 4.9, < 4.9.35; ≥ 5.0, < 5.0.31; ≥ 5.1, < 5.1.28; ≥ 5.2, < 5.2.30; ≥ 5.3, < 5.3.27; ≥ 5.4, < 5.4.25
Disclosed
Last updated
CVSS 3.1 vector
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Written automatically on 17 November 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Sources of this advisory

The sources report that WordPress Core has a race condition in full-package core upgrades that lets unauthenticated attackers execute code on the server. CISA lists CVE-2026-119977 as exploited.

What is affected

The vulnerability is tracked as CVE-2026-119977 and affects WordPress Core. The description in the public sources says versions 4.7 through 7.1.3 are vulnerable. The affected version ranges given in the facts are:

  • ≥ 4.7, < 4.7.39
  • ≥ 4.8, < 4.8.34
  • ≥ 4.9, < 4.9.35
  • ≥ 5.0, < 5.0.31
  • ≥ 5.1, < 5.1.28
  • ≥ 5.2, < 5.2.30
  • ≥ 5.3, < 5.3.27
  • ≥ 5.4, < 5.4.25

The fixed releases are listed in the vendor advisory, so please use it to confirm whether your installation is covered.

What the flaw allows

The sources describe a time-of-check time-of-use race condition, classified as CWE-367. WordPress uses predictable, web-accessible staging paths during full-package core upgrades. According to the description, this makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

The CVSS 3.1 base score is 8.1, which is a high severity rating. The vector indicates that the attack is possible over the network without authentication or user interaction, that attack complexity is high, and that the impact on confidentiality, integrity and availability is high. The high attack complexity is consistent with the flaw depending on an upgrade being in progress.

Exploitation

CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-11-03. CISA's stated deadline for US federal agencies to act is 2026-11-06. CISA lists the use in ransomware campaigns as unknown. The vulnerability was disclosed on 2026-10-31.

The CISA entry asks for mitigations to be applied in line with vendor instructions. It also asks organisations to evaluate the internet exposure of each asset.

What to do

Check which version of WordPress Core each of your sites runs and compare it with the ranges above and with the vendor advisory. Where a site is affected, follow the vendor's instructions and use the fixed releases it lists. See the mitigation section for the sources.

What to do

Follow the vendor instructions in the WordPress announcement, which is the vendor advisory and lists the fixed releases. Compare your installed version with the affected ranges above before and after the change.

Further details are in the Wordfence vulnerability entry and in the CISA Known Exploited Vulnerabilities catalogue.

Sources

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.