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

Recommended actionPatch now

CISA confirms exploitation in the wild and lists 2026-11-06 as the remediation due date.

Patch available

What, why and how

WordPress WordPress Core contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window. This is due to predictable, web-accessible staging paths used during full-package core upgrades.

What

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Why

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.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

Confirmed in the wild

CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-11-03.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Time-of-check Time-of-use (TOCTOU) Race Condition → execute code or commands in the affected security context
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: High: exploitation depends on specific conditions
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-367 ↗
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition. 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.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.

NetworkUnauthenticatedRemote code executionCWE-367CISA KEV

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-114575Known-exploited evidence recorded

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.

Official EUVD record ↗

BSI · German · WID-SEC-2026-4283WordPress: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in WordPress ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗

Canadian Centre for Cyber Security · English · AV26-1117WordPress security advisory (AV26-1117)

As of October 31, 2026, WordPress is affected by a vulnerability in the following product: On November 3, 2026, Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-119977 to their Known Exploited Vulnerabilities (KEV) Database.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1480Avis du CERT-FR

Une vulnérabilité a été découverte dans Alpine. Elle permet à un attaquant de provoquer un contournement de la politique de sécurité.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1420Avis du CERT-FR

De multiples vulnérabilités ont été découvertes dans WordPress. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗

CSIRT Italia · Italian · wordpress-rilevato-sfruttamento-in-rete-della-cve-2026-119977WordPress: rilevato sfruttamento in rete della CVE-2026-119977

In dettaglio, la vulnerabilità identificata tramite la CVE-2026-119977 - di tipo "Time-of-check Time-of-use (TOCTOU) Race Condition" e con score CVSS v3.1 pari a 8.1 - è dovuta all'utilizzo di percorsi di staging prevedibili e accessibili via web durante gli aggiornamenti completi di WordPress Core. Un attaccante remoto non autenticato potrebbe accedere alla directory di staging e richiamare specifici file durante la finestra temporale in cui è in corso l'aggiornamento, riuscendo a ottenere l'esecuzione di codice arbitrario sul server.

Official advisory ↗

KISA KrCERT/CC · Korean · KNVD-7046WordPress 제품 보안 업데이트 권고

WordPress에서 발생하는 Time-of-check Time-of-use (TOCTOU) Race Condition 취약점(CVE-2026-119977) [1]~[3]

Official advisory ↗

KISA KrCERT/CC · Korean · KNVD-7044美 CISA 발표 주요 Exploit 정보공유(Update. 2026-11-03)

WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability

Official advisory ↗

NCSC-NL · Dutch · NCSC-2026-0466Kwetsbaarheid verholpen in WordPress Core

De kwetsbaarheid maakt misbruik mogelijk van een TOCTOU-racecondition (Time-of-Check to Time-of-Use) tijdens volledige WordPress Core-upgrades. Hierdoor kan een niet-geauthenticeerde aanvaller op afstand code uitvoeren op de server door het korte upgradevenster te misbruiken waarin de stagingdirectories via het web toegankelijk zijn. Voor succesvolle exploitatie moet de aanvaller erin slagen om tijdens dit beperkte upgradevenster de racecondition te benutten. CISA heeft bevestigd dat CVE-2026-119977 actief wordt misbruikt en heeft de kwetsbaarheid op 3 november 2026 toegevoegd aan de Known Exploited Vulnerabilities (KEV)-catalogus.

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: WordPress: 5.4.0 ≤ 5.4.24, 5.2.0 ≤ 5.2.29, 4.9.0 ≤ 4.9.34, 5.5.0 ≤ 5.5.23, 6.6.0 ≤ 6.6.10, 5.8.0 ≤ 5.8.18, 6.3.0 ≤ 6.3.13, 6.2.0 ≤ 6.2.14, 4.8.0 ≤ 4.8.33, 5.3.0 ≤ 5.3.26, 7.1.0 ≤ 7.1.3, 6.8.0 ≤ 6.8.11, 5.1.0 ≤ 5.1.27, 6.4.0 ≤ 6.4.13, 4.7.0 ≤ 4.7.38, 6.7.0 ≤ 6.7.10, 5.0.0 ≤ 5.0.30, 6.0.0 ≤ 6.0.17, 6.9.0 ≤ 6.9.10, 5.6.0 ≤ 5.6.22, 6.5.0 ≤ 6.5.13, 5.7.0 ≤ 5.7.20, 6.1.0 ≤ 6.1.15, 5.9.0 ≤ 5.9.19, 7.0.0 ≤ 7.0.7
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

WordPress 7.1.4 | WordPress News →Original publisher ↗Searchable text snapshot · Captured 13 Nov 2026This security release features fixes for multiple issues. Because this is a security release, it is recommended that you update your sites immediately. You can download WordPress 7.1.4 from WordPress.org , or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support a

Evidence and provenance

Published 31 Oct 2026 · Last source change 4 Nov 2026, 04:56 UTC · CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-10-31

European sourceENISA EUVD · EUVD-2026-114575

Product sourceCISA KEV

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

4 Nov 2026, 17:00 UTC
ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.
Before
not listed in ENISA EUVD known-exploited dataset
After
listed in ENISA EUVD known-exploited dataset (EUVD-2026-114575)
ENISA EUVD ↗
4 Nov 2026, 04:56 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: core.trac.wordpress.org/class-wp-upgrader.php; added patch: core.trac.wordpress.org/update-core.php; 1 further additions.
Before
no authoritative guidance recorded
After
patch: core.trac.wordpress.org/class-wp-upgrader.php · patch: core.trac.wordpress.org/update-core.php · remediation: core.trac.wordpress.org/class-wp-upgrader.php
security@wordfence.com ↗
4 Nov 2026, 04:56 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
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 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
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 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CISA KEV ↗
4 Nov 2026, 04:56 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
security@wordfence.com ↗
4 Nov 2026, 04:56 UTC
Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-1117.
Before
remediation: cyber.gc.ca/wordpress-security-advisory-av26-1117
After
no authoritative guidance recorded
CISA KEV ↗
4 Nov 2026, 04:56 UTC
Remediation statusRemediation status changed from Mitigation available to Awaiting fix.
Before
Mitigation available
After
Awaiting fix
CISA KEV ↗
3 Nov 2026, 21:36 UTC
Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
Before
Awaiting fix
After
Mitigation available
Canadian Centre for Cyber Security ↗
3 Nov 2026, 20:58 UTC
Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-1117.
Before
remediation: cyber.gc.ca/wordpress-security-advisory-av26-1117
After
no authoritative guidance recorded
CISA KEV ↗
3 Nov 2026, 20:58 UTC
Remediation statusRemediation status changed from Mitigation available to Awaiting fix.
Before
Mitigation available
After
Awaiting fix
CISA KEV ↗
31 Oct 2026, 09:04 UTC
ENISA EUVD mappingEUVD-2026-114575 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2026-114575"}
ENISA EUVD ↗
31 Oct 2026, 05:33 UTC
CISA KEV stateCISA KEV now confirms exploitation in the wild.
Before
not listed in CISA KEV
After
listed in CISA KEV since 2026-11-03
CISA KEV ↗
31 Oct 2026, 05:33 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2026-10-31CVE published

2026-11-03Added to CISA KEV

2026-11-04Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-114575↗Vendor CSAF · Red Hat Product Security↗CISA KEV record↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability

Published severity in operational context

Evidence used

Compensating controls

Verification

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-114575

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication