CriticalCVE-2026-119977

WordPress: Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-2026-119977)

Published 02.11.2026Last modified 04.11.2026In CISA KEV since 03.11.2026Sources: BSI

What is affected, what to do

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades.

The vulnerability is being actively exploited; treat it as a priority. Update wordpress to version 4.7.39, WordPress to version 4.7.39. Immediate actions, mitigation and detection rules are in the runbook below.

Affected: WordPress lte 4.7.0..4.7.38
WordPress lte 4.8.0..4.8.33
WordPress lte 4.9.0..4.9.34
WordPress lte 5.0.0..5.0.30
WordPress lte 5.1.0..5.1.27
WordPress lte 5.2.0..5.2.29
WordPress lte 5.3.0..5.3.26
WordPress lte 5.4.0..5.4.24
WordPress lte 5.5.0..5.5.23
WordPress lte 5.6.0..5.6.22
WordPress lte 5.7.0..5.7.20
WordPress lte 5.8.0..5.8.18
WordPress lte 5.9.0..5.9.19
WordPress lte 6.0.0..6.0.17
WordPress lte 6.1.0..6.1.15
WordPress lte 6.2.0..6.2.14
WordPress lte 6.3.0..6.3.13
WordPress lte 6.4.0..6.4.13
WordPress lte 6.5.0..6.5.13
WordPress lte 6.6.0..6.6.10
WordPress lte 6.7.0..6.7.10
WordPress lte 6.8.0..6.8.11
WordPress lte 6.9.0..6.9.10
WordPress lte 7.0.0..7.0.7
WordPress lte 7.1.0..7.1.3

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

8.1

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: NVD, CVSS v3

8.1

CVSS v3

Severity High on the scale from 0 to 10.

Source: BSI

1.2 %

EPSS score

Moderate — model estimates 1-10% exploitation likelihood.

Source: FIRST EPSS, percentile 67.2

Show all metrics

Severity: Critical
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 206.61 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 8.1 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 8.1
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 1.2 %; Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 67.2; High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: Actively exploited
Published: 02.11.2026
In CISA KEV since The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: 03.11.2026
CISA assessment (SSVC): Exploitation: active · not automatable · Technical impact: total; Source: CISA Vulnrichment, as of 3 November 2026
CWE CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect. Read in glossary: CWE-367

Response and mitigation

Why act now?

Prioritisation rationale

The flaw is network-reachable without authentication and yields full code execution on the server. Its high attack complexity comes from having to win a timing window during a core upgrade. Because automatic background updates make that window predictable and attackers can poll at scale, the complexity is lower in practice than the rating suggests. Exploitation likelihood is currently assessed as moderate, and CISA does not flag known ransomware use. Typical targets are widely deployed, internet-facing WordPress sites without a WAF in front, such as marketing pages, campaign microsites and agency-managed hosting. Rate it high for externally reachable instances with auto-updates enabled, and put the path block in place before patching. Purely internal or statically served instances can follow later.

01
Runbook step 1
Immediate response (0-24 h)
- Inventory: Enumerate every WordPress instance (including marketing microsites, agency-hosted sites and staging systems) and check the core version, e.g. wp core version --allow-root or grep wp_version wp-includes/version.php. NVD lists 4.7 through 7.1.3 inclusive as affected. The listed branch ranges run up to, for example, 4.7.38 and 5.4.24.
- Block the staging path before patching: The fix itself arrives via a core upgrade, and that upgrade window is exactly the attack surface. Deny web access to /wp-content/upgrade/ (and /wp-content/upgrade-temp-backup/ if present) at the web server or WAF first. Only then upgrade.
- Apply the patch: A patch is available from the vendor — look up the fixed release per branch in the WordPress security advisory. Run the update deliberately with WP-CLI (wp core update) during a maintenance window. Ideally put an IP allowlist or maintenance page in front at the reverse proxy.
- Control automatic core updates temporarily: Unprotected sites self-update at predictable times, which lets attackers schedule their race. Until the path block is live, set define('AUTOMATIC_UPDATER_DISABLED', true); in wp-config.php and roll out updates manually behind the block. Re-enable automatic updates afterwards.
- Compromise check: On any instance that ran a full-package upgrade during the affected period, run wp core verify-checksums and hunt for unknown PHP files in wp-content/ and wp-content/uploads/. If you find any, treat the instance as compromised: isolate it and rotate database credentials, admin credentials and salts (AUTH_KEY etc.).
02
Runbook step 2
Mitigation layers
- Web server config: For nginx, use location ^~ /wp-content/upgrade { deny all; }. For Apache, add Require all denied in wp-content/upgrade/.htaccess. Also block PHP execution under wp-content/upgrade and wp-content/uploads across the board (location ~* ^/wp-content/(upgrade|uploads)/.*\.php$ { deny all; }).
- WAF/IPS: Add a block-and-log rule for any external request matching ^/wp-content/upgrade(-temp-backup)?/. These paths have no legitimate external traffic. Also rate-limit repeated requests for non-existent paths under /wp-content/, because winning the race requires heavy polling.
- Filesystem hardening: Give the web server user read-only access to core files wherever possible. Perform updates through a separate deploy user or a CI/CD pipeline (DISALLOW_FILE_MODS in production, with deploys replacing in-place upgrades).
- Network segmentation: Restrict web server egress to required destinations (WordPress.org update servers, the database). This hampers reverse shells and second-stage downloads after successful code execution.
- Operational process: Run core updates only in defined maintenance windows with access restrictions in place. For shared or agency hosting, require the provider to confirm the path block (an NIS2 supply-chain requirement).
03
Runbook step 3
Detection rules
- Web access logs: Any external request to /wp-content/upgrade/ ending in .php is highly suspicious. Watch especially for bursts of 404s followed by a 200, which indicates polling until the race is won. SPL: index=web uri_path="/wp-content/upgrade/*" | stats count values(status) by src_ip, uri_path.
- Process ancestry (EDR/auditd): Alert when php-fpm, apache2 or httpd spawns sh, bash, curl, wget, nc or python. Sigma shape: ParentImage|endswith: ['/php-fpm','/apache2','/httpd'] AND Image|endswith: ['/sh','/bash','/curl','/wget'].
- File integrity (auditd/FIM): Watch the staging path with -w /var/www/html/wp-content/upgrade -p wa -k wp_upgrade. Alert on new PHP files outside update windows or on writes by any user other than the deploy account. After every update, feed wp core verify-checksums results into monitoring.
- Network telemetry (Zeek/Suricata): Hunt http.log for uri values prefixed /wp-content/upgrade/ from external sources. Correlate new outbound connections from the web server to unfamiliar destinations shortly after a core update.
- WordPress layer: Review unexpected new administrator accounts and changes to wp-config.php or must-use plugins (wp-content/mu-plugins/) shortly after any upgrade event.

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

Source: BSI WID Portal

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
WordPress Foundation	WordPress	`4.7.0 – ≤ 4.7.38` `4.8.0 – ≤ 4.8.33` `4.9.0 – ≤ 4.9.34` `5.0.0 – ≤ 5.0.30` `5.1.0 – ≤ 5.1.27` `5.2.0 – ≤ 5.2.29` `5.3.0 – ≤ 5.3.26` `5.4.0 – ≤ 5.4.24` `5.5.0 – ≤ 5.5.23` `5.6.0 – ≤ 5.6.22` `5.7.0 – ≤ 5.7.20` `5.8.0 – ≤ 5.8.18` `5.9.0 – ≤ 5.9.19` `6.0.0 – ≤ 6.0.17` `6.1.0 – ≤ 6.1.15` `6.2.0 – ≤ 6.2.14` `6.3.0 – ≤ 6.3.13` `6.4.0 – ≤ 6.4.13` `6.5.0 – ≤ 6.5.13` `6.6.0 – ≤ 6.6.10` `6.7.0 – ≤ 6.7.10` `6.8.0 – ≤ 6.8.11` `6.9.0 – ≤ 6.9.10` `7.0.0 – ≤ 7.0.7` `7.1.0 – ≤ 7.1.3`	— — — — — — — — — — — — — — — — — — — — — — — — —
wordpress	wordpress	`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` `5.5 – < 5.5.24` `5.6 – < 5.6.23` `5.7 – < 5.7.21` `5.8 – < 5.8.19` `5.9 – < 5.9.20` `6.0 – < 6.0.18` `6.1 – < 6.1.16` `6.2 – < 6.2.15` `6.3 – < 6.3.14` `6.4 – < 6.4.14` `6.5 – < 6.5.14` `6.6 – < 6.6.11` `6.7 – < 6.7.11` `6.8 – < 6.8.12` `6.9 – < 6.9.11`	`4.7.39` `4.8.34` `4.9.35` `5.0.31` `5.1.28` `5.2.30` `5.3.27` `5.4.25` `5.5.24` `5.6.23` `5.7.21` `5.8.19` `5.9.20` `6.0.18` `6.1.16` `6.2.15` `6.3.14` `6.4.14` `6.5.14` `6.6.11` `6.7.11` `6.8.12` `6.9.11`

From bundled advisories, not CVE-specific (1)

Product list of a bundled advisory that does not state which product this CVE affects.

Products from bundled advisories
		Affected versions	Fixed in
wordpress	wordpress	`< 7.1.4`	`7.1.4`

Vendors and products

Affected operating systems

Affected operating systems

Linux	debian	wordpress	`trixie`

Weakness classes (CWE)

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
Base
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Entry at MITRE CWE-367

Public exploit references

Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

Public exploit references

CISA KEV Catalog	CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov	actively exploited	03.11.2026

References & sources

core.trac.wordpress.orgbrowser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.phpProduct
core.trac.wordpress.orgbrowser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.phpProduct
core.trac.wordpress.orgbrowser/tags/7.1.3/src/wp-admin/includes/update-core.phpProduct
core.trac.wordpress.orgbrowser/tags/7.1.3/src/wp-admin/setup-config.phpProduct
core.trac.wordpress.orgbrowser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.phpPatch
core.trac.wordpress.orgbrowser/tags/7.1.4/src/wp-admin/includes/update-core.phpPatch
wordpress.orgWordPress 7.1.4pwn-watch, Release notes
wordfence.comthreat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a…Third-party advisory
cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-1199…government-resource, US government resource
wordfence.comthreat-intel/vulnerabilities/wordpress-core/wordpress-core-470-…Third-party advisory, Third-party advisory
pwn.watchpwn.watch: WordPress 7.1.4 security release: upgrade-window RCE under exploitation attempts, plus stored XSS fixespwn-watch
cisa.govCISA Adds One Known Exploited Vulnerability to Catalog (CVE-2026-119977)pwn-watch
thehackernews.comWordPress RCE Flaw Draws Nearly 63,000 Attack Attempts in Just 24 Hourspwn-watch
securityweek.comFresh WordPress Vulnerability in Attackers' Crosshairspwn-watch
wordfence.comWordPress 7.1.4 Patches Unauthenticated Upgrade-Window RCE; Exploitation Attempts Detected After Releasepwn-watch
cybersecuritynews.comHackers Actively Exploiting WordPress Remote Code Execution Flaw Just Hours After Patch Releasepwn-watch
wordpress.orgWordPress 7.1.4 (HelpHub release notes)pwn-watch

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

04.11.2026Initial analysis by NVDNVD

Newly listed as affected:

WordPress (4.7 – before 4.7.39; 4.8 – before 4.8.34; 4.9 – before 4.9.35; 5.0 – before 5.0.31; 5.1 – before 5.1.28; 5.2 – before 5.2.30; 5.3 – before 5.3.27; 5.4 – before 5.4.25; 5.5 – before 5.5.24; 5.6 – before 5.6.23; 5.7 – before 5.7.21; 5.8 – before 5.8.19; 5.9 – before 5.9.20; 6.0 – before 6.0.18; 6.1 – before 6.1.16; 6.2 – before 6.2.15; 6.3 – before 6.3.14; 6.4 – before 6.4.14; 6.5 – before 6.5.14; 6.6 – before 6.6.11; 6.7 – before 6.7.11; 6.8 – before 6.8.12; 6.9 – before 6.9.11; 7.0 – before 7.0.8; 7.1 – before 7.1.4)

New references:

and 6 more references

Show 17 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Product configuration	added	—	OR cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 4.7 up to (excluding) 4.7.39 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 4.8 up to (excluding) 4.8.34 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 4.9 up to (excluding) 4.9.35 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.0 up to (excluding) 5.0.31 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.1 up to (excluding) 5.1.28 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.2 up to (excluding) 5.2.30 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.3 up to (excluding) 5.3.27 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.4 up to (excluding) 5.4.25 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.5 up to (excluding) 5.5.24 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.6 up to (excluding) 5.6.23 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.7 up to (excluding) 5.7.21 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.8 up to (excluding) 5.8.19 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 5.9 up to (excluding) 5.9.20 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.0 up to (excluding) 6.0.18 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.1 up to (excluding) 6.1.16 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.2 up to (excluding) 6.2.15 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.3 up to (excluding) 6.3.14 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.4 up to (excluding) 6.4.14 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.5 up to (excluding) 6.5.14 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.6 up to (excluding) 6.6.11 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.7 up to (excluding) 6.7.11 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.8 up to (excluding) 6.8.12 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 6.9 up to (excluding) 6.9.11 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 7.0 up to (excluding) 7.0.8 cpe:2.3:a:wordpress:wordpress::::::::* versions from (including) 7.1 up to (excluding) 7.1.4
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162 Types: Product
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378 Types: Product
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549 Types: Product
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282 Types: Product
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346 Types: Patch
Reference type	added	—	Wordfence: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545 Types: Patch
Reference type	added	—	Wordfence: https://wordpress.org/news/2026/10/wordpress-7-1-4/ Types: Release Notes
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162 Types: Permissions Required, Product
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378 Types: Permissions Required, Product
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549 Types: Permissions Required, Product
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282 Types: Permissions Required, Product
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346 Types: Patch, Permissions Required
Reference type	changed	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545 Types: Permissions Required	nvd-ai-agent-0.4.0-gemma-4-31B-it: https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545 Types: Patch, Permissions Required
Reference type	added	—	CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977 Types: US Government Resource
Reference type	added	—	Wordfence: https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve Types: Third Party Advisory
Reference type	added	—	CISA-ADP: https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution Types: Third Party Advisory

Source identifier: nvd@nist.gov

04.11.2026Record modifiedCISA ADP

CISA assessment (SSVC): exploitation: active, automatable: no

Show 2 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
SSVC assessment	removed	{"id":"CVE-2026-119977","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T20:50:05.434105Z"}	—
SSVC assessment	added	—	{"id":"CVE-2026-119977","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T00:00:00+00:00"}

Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

03.11.2026CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD
Type Action Before After
Date Added added
—
2026-11-03
Due Date added
—
2026-11-03
Required Action added
—
2026-11-03
Vulnerability Name added
—
2026-11-03
Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

Individual changes of this event as published by NVD
Type	Action	Before	After
Date Added	added	—	2026-11-03
Due Date	added	—	2026-11-03
Required Action	added	—	2026-11-03
Vulnerability Name	added	—	2026-11-03

03.11.2026Record modifiedCISA ADP

CISA assessment (SSVC): exploitation: active, automatable: no

New references:

Show 3 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Reference	added	—	https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977
Reference	added	—	https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution
SSVC assessment	added	—	{"id":"CVE-2026-119977","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T20:50:05.434105Z"}

Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

31.10.2026ReceivedWordfence

CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness type: CWE-367

Description added or changed

New references:

and 4 more references

Show 12 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.
CVSS	added	—	AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness type (CWE)	added	—	CWE-367
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119977.json">CVE-2026-119977</a>
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346
Reference	added	—	https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545
Reference	added	—	https://wordpress.org/news/2026/10/wordpress-7-1-4/
Reference	added	—	https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve

Source identifier: security@wordfence.com

Linked CVEs

Linked CVEs

Critical	CVE-2026-119977	WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution	8.1	Actively exploited

Linked advisories

NCSC-2026-0466 [1.00] [L/H] Kwetsbaarheid verholpen in WordPress CoreNCSC-NL04.11.2026
CISA Confirms Hackers Exploiting WordPress Core Flaw During Software UpgradesThe Hacker News04.11.2026

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-119977"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119977.svg?lang=en" alt="CVE-2026-119977 – NEOSEC Intel" height="20"></a>

What is affected, what to do

Metrics

Response and mitigation

Prioritisation rationale

Immediate response (0-24 h)

Mitigation layers

Detection rules

Detection rules

Classification under NIS2 and CRA

Description

Affected products

Vendors and products

Affected operating systems

Weakness classes (CWE)

Public exploit references

References & sources

Changes to this CVE

Linked CVEs

Linked advisories