CVE-2026-119977: WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition
WordPress Core · listed in the CISA catalog of actively exploited vulnerabilities since 2026-11-03.
- CVSS v3.1 (CVE record)
- 8.1
- high
- EPSS (exploit probability, 30 days)
- 8.1%
- higher than 94.9% of all CVEs
- Added to CISA KEV
- 2026-11-03
- US federal due date 2026-11-06
- Ubuntu priority
- –
CVE-2026-119977 explained
CVE-2026-119977 is a time-of-check time-of-use race condition in WordPress Core versions 4.7 through 7.1.3. Full-package core upgrades use predictable, web-accessible staging paths, which can let unauthenticated attackers execute code on the server during the upgrade window. CISA lists it as a known exploited vulnerability.
Impact
An unauthenticated attacker over the network can execute code on the server during the window of a full-package core upgrade. No user interaction is needed. Attack complexity is rated high. Successful exploitation has high impact on confidentiality, integrity and availability of the affected system. CISA has added this CVE to its Known Exploited Vulnerabilities catalog. Whether it is used in ransomware campaigns is unknown.
Who is affected
The wordpress source package is affected on Debian. Debian 13 (trixie) has a fix in 6.8.12+dfsg1-0+deb13u1. Debian 14 (forky), the Debian testing distribution, has a fix in 7.1.4+dfsg1-1. Debian 12 (bookworm) is affected, and no fixed version has been published for it yet. Upstream, WordPress Core versions 4.7 through 7.1.3 are affected.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- WordPress Foundation WordPressAffectedFixed in
- ≥ 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
not stated
| Product | Affected | Fixed in |
|---|---|---|
| WordPress Foundation WordPress |
| not stated |
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Debian 14 (forky)·wordpress
testing distribution
Fixed: 7.1.4+dfsg1-1
Debian 13 (trixie)·wordpress
Fixed: 6.8.12+dfsg1-0+deb13u1
Debian 12 (bookworm)·wordpress
Status: no fixed version published · Debian tracker
What to do
- Identify all hosts running the
wordpresspackage or WordPress Core 4.7 through 7.1.3. - On Debian 13 (trixie), update
wordpressto6.8.12+dfsg1-0+deb13u1or later. - On Debian 14 (forky), update
wordpressto7.1.4+dfsg1-1or later. - On Debian 12 (bookworm), apply the vendor's mitigations and track the Debian advisory for a fixed package.
- Review internet exposure of each WordPress site and restrict access where possible.
- Check affected servers for signs of compromise, since the vulnerability is known to be exploited.
Debian 12 (bookworm) has no fixed wordpress package yet. Apply mitigations according to the vendor's instructions, as CISA requires. Limit network exposure of affected sites. If mitigations are unavailable, CISA advises discontinuing use of the product. Watch the Debian advisory and install the fixed package once it is published.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace wordpress with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="wordpress"'2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="wordpress"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
No fixed version yet on one release
Debian 12 (bookworm): no fixed version of wordpress yet, so every installed version there is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/i…
- If the server does not need the package, remove it, or replace it with a maintained alternative.
- Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.
This page updates automatically when Ubuntu or Debian publish a fix.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Questions about CVE-2026-119977
- Do attackers need an account on the WordPress site?
- No. The description states that unauthenticated attackers can execute code on the server. No privileges or user interaction are required, though attack complexity is rated high.
- Is this vulnerability exploited in the wild?
- Yes. CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on 2026-11-03, with a US federal due date of 2026-11-06. Known ransomware use is listed as unknown.
- Is Debian 12 (bookworm) fixed?
- Not yet. No fixed version of
wordpresshas been published for Debian 12 (bookworm). Debian 13 (trixie) and Debian 14 (forky) have fixed versions.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/i… (1)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/i… (2)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/i… (3)
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/s…
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/i… (1)
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/i… (2)
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.