{"basis":"claimed","id":"CVE-2026-119977","name":"WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability","vendorProject":"WordPress","product":"WordPress Core","publishedAt":"2026-10-31","cvss":{"score":8.1,"severity":"HIGH","version":"3.1"},"exploited":{"kevAdded":"2026-11-03","dueDate":"2026-11-06","ransomware":false},"epss":{"score":0.006,"percentile":0.48701,"date":"2026-11-02"},"coverage":{"cloudflare":{"status":"none","firstOn":null,"daysToRule":null},"aws":{"status":"none","firstOn":null,"daysToRule":null},"azure":{"status":"none","firstOn":null,"daysToRule":null},"google":{"status":"none","firstOn":null,"daysToRule":null},"fastly":{"status":"none","firstOn":null,"daysToRule":null},"f5":{"status":"none","firstOn":null,"daysToRule":null},"akamai":{"status":"no_source","firstOn":null,"daysToRule":null},"crs":{"status":"none","firstOn":null,"daysToRule":null}},"title":"WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution","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.","cwes":["CWE-367"],"vendors":[{"vendor":"cloudflare","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"aws","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"azure","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"google","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"fastly","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"f5","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"akamai","status":"no_source","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"crs","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]}],"updatedAt":"2026-11-03T22:17:37.907Z","cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","ssvc":null,"kevAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.","kevNotes":"https://wordpress.org/news/2026/10/wordpress-7-1-4 ; https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-119977","references":[{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346","name":null,"tags":[]},{"url":"https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545","name":null,"tags":[]},{"url":"https://wordpress.org/news/2026/10/wordpress-7-1-4/","name":null,"tags":[]}],"affected":[{"vendor":"WordPress Foundation","product":"WordPress","affected":["4.7.0 through 4.7.38","4.8.0 through 4.8.33","4.9.0 through 4.9.34","5.0.0 through 5.0.30","5.1.0 through 5.1.27","5.2.0 through 5.2.29","5.3.0 through 5.3.26","5.4.0 through 5.4.24"],"fixed":[]}],"briefing":{"status":{"id":"known_exploited","label":"Known exploited"},"why":"CISA lists CVE-2026-119977 as exploited in the wild since 2026-11-03. It is reachable over the network without credentials or any user interaction (CVSS 8.1). No edge WAF vendor names it in a changelog, so default managed rules may or may not catch it.","who":"Teams running WordPress Foundation WordPress (4.7.0 through 4.7.38; 4.8.0 through 4.8.33; 4.9.0 through 4.9.34; more in the CVE record). Prioritise internet-facing instances.","what_to_do":[{"text":"Find the version you run. In the site directory (WP-CLI; plugins listed with versions):","command":{"where":"In the site directory (WP-CLI; plugins listed with versions)","command":"wp core version && wp plugin list"}},{"text":"Apply the vendor's fix; the advisory lists the affected and fixed versions.","href":"https://wordpress.org/news/2026/10/wordpress-7-1-4","linkText":"wordpress.org"},{"text":"CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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. US federal agencies must act by 2026-11-06."},{"text":"Review exposed instances for signs of compromise: it was exploited before many systems were patched, and a later patch does not undo access already gained."},{"text":"Do not rely on WAF defaults: no edge vendor names this CVE. Restrict access to the vulnerable component or add a custom rule until it is patched.","href":"#edge","linkText":"Edge coverage"},{"text":"Check which WAF sits in front of your site and whether it covers this CVE.","href":"#check","linkText":"Check your domain"}],"evidence":[{"heading":"CVE record","text":"CVSS 3.1 8.1 (high). Weakness: CWE-367.","links":[{"label":"CVE-2026-119977","href":"https://www.cve.org/CVERecord?id=CVE-2026-119977"},{"label":"NVD","href":"https://nvd.nist.gov/vuln/detail/CVE-2026-119977"}]},{"heading":"Vendor advisory","text":"Fixes and mitigations the CVE record links to. Check affected builds against the vendor, including backports.","links":[{"label":"wordpress.org","href":"https://wordpress.org/news/2026/10/wordpress-7-1-4"},{"label":"wordfence.com","href":"https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution"},{"label":"cisa.gov","href":"https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk"},{"label":"cisa.gov","href":"https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk"}]},{"heading":"Exploit evidence","text":"No public exploit code found in Exploit-DB, Metasploit, nuclei-templates or GitHub. That does not mean none exists.","links":[]},{"heading":"Seen exploited","text":"Listed in an independent exploited-vulnerability catalog on 3 Nov 2026. Claimed in 1 Telegram post (unverified).","links":[]},{"heading":"CISA KEV","text":"Added 2026-11-03, federal due date 2026-11-06 (catalog 2026.11.03, checked 2026-11-03).","links":[{"label":"CISA KEV catalog","href":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-119977"}]},{"heading":"EPSS","text":"0.60% probability of exploitation activity in the next 30 days, higher than 48% of CVEs (2026-11-02).","links":[{"label":"FIRST EPSS","href":"https://api.first.org/data/v1/epss?cve=CVE-2026-119977"}]},{"heading":"WAF vendor statements","text":"No edge vendor changelog names it.","links":[]}],"agent_prompt":"Assess whether the infrastructure available to you is affected by CVE-2026-119977 (WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability). Perform a read-only assessment within your authorized access. Do not send exploit traffic, scan third-party systems, change configuration or restart services.\n\n1. Verify the CVE record at https://www.cve.org/CVERecord?id=CVE-2026-119977 and the vendor advisory. Establish affected and fixed versions, including vendor backports. The record lists: WordPress Foundation WordPress: affected 4.7.0 through 4.7.38; 4.8.0 through 4.8.33; 4.9.0 through 4.9.34; 5.0.0 through 5.0.30. Cite sources and retrieval dates; flag anything you cannot verify.\n2. Inventory deployments of WordPress WordPress Core: asset, environment, owner where known, installed version or build, and how you confirmed it (package metadata, a version endpoint, image tags), e.g. `wp core version && wp plugin list` (in the site directory (WP-CLI; plugins listed with versions)). An image tag alone does not prove the running version.\n3. Identify which deployments are reachable from the internet or untrusted networks, and through which paths (direct origin, load balancer, CDN or WAF).\n4. Assess compensating controls separately from patch status. Current edge WAF coverage for this CVE: no edge WAF vendor names it. Live data: https://cve.vigilbase.com/api/v1/cves/CVE-2026-119977. Check whether the rule is enabled and in block mode on each path, and whether any path bypasses the WAF. A WAF rule is not a patch.\n5. It is known exploited (CISA KEV): review logs on exposed instances for signs of exploitation before and after patching.\n\nReturn a short summary and a table: asset | version/build | assessment (affected, fixed, not applicable, unknown) | exposure | compensating control | evidence | next action. List what you could not assess and the access needed to resolve it. Do not infer absence of compromise from patch status or a lack of alerts.\n\nRemediation guidance: Apply the vendor's fix; the advisory lists the affected and fixed versions. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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. US federal agencies must act by 2026-11-06.\nMore: https://cve.vigilbase.com/cve/CVE-2026-119977"},"measured":[],"sightings":{"honeypot":null,"catalog":"2026-11-03","reports":[],"telegram":{"posts":1,"last":"2026-11-02"},"days":{"honeypot":[],"reports":[],"telegram":["2026-11-02"]}},"social":{"total":42,"first_seen":"2026-11-03T00:15:39.000Z","daily":[{"day":"2026-10-21","posts":0},{"day":"2026-10-22","posts":0},{"day":"2026-10-23","posts":0},{"day":"2026-10-24","posts":0},{"day":"2026-10-25","posts":0},{"day":"2026-10-26","posts":0},{"day":"2026-10-27","posts":0},{"day":"2026-10-28","posts":0},{"day":"2026-10-29","posts":0},{"day":"2026-10-30","posts":0},{"day":"2026-10-31","posts":0},{"day":"2026-11-01","posts":0},{"day":"2026-11-02","posts":0},{"day":"2026-11-03","posts":42}],"top_posts":[{"source":"mastodon","kind":"post","url":"https://infosec.exchange/@overflo_ws/117554465092513588","author":"overflo_ws@infosec.exchange","author_name":"overflo.ws","avatar_url":"https://files.mastodon.social/cache/accounts/avatars/117/455/795/442/113/826/original/c2d3282e2311230c.png","text":"Added to CISA's Known Exploited Vulnerabilities catalog: CVE-2026-119977 WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability CVSS 8.1 (High). EPSS 0.6%. US federal agencies must remediate by 2026-11-06. WordPress WordPress Core contains a tim…","engagement":1,"posted_at":"2026-11-03T20:46:26.000Z"},{"source":"hn","kind":"post","url":"https://news.ycombinator.com/item?id=50357772","author":"acossta","author_name":null,"avatar_url":null,"text":"CISA: WordPress core upgrade-window RCE CVE-2026-119977 exploited in the wild","engagement":1,"posted_at":"2026-11-03T20:31:52.000Z"},{"source":"x","kind":"post","url":"https://x.com/thecyberseckyle/status/2117753785980252528","author":"thecyberseckyle","author_name":"Kyle R | Cyber & IT","avatar_url":"https://pbs.twimg.com/profile_images/2106141649055150081/PTigrvZw_bigger.jpg","text":"CISA added WordPress Core CVE-2026-119977 to KEV. A flaw in upgrade staging can allow unauthenticated code execution during updates. Verify 7.1.4 or a fixed branch release and review upgrade logs. #Cybersecurity #Infosec #WordPress\n\nhttps://t.co/Rz8j0eV2lw","engagement":0,"posted_at":"2026-11-03T23:00:23.000Z"},{"source":"x","kind":"post","url":"https://x.com/cubillas888/status/2117753699669774666","author":"cubillas888","author_name":"cubillas","avatar_url":"https://pbs.twimg.com/profile_images/2108424075504754688/p6oOOeDY_bigger.jpg","text":"CISA KEV exploited: WordPress core CVE-2026-119977 added Nov 3, federal due date Nov 6. CISA says unauthenticated attackers could run code on the server during the upgrade window.\n1. Check Dashboard > Updates\n2. Move to 7.1.4+\n3. Older branches: backports are rolling out","engagement":0,"posted_at":"2026-11-03T23:00:02.000Z"},{"source":"x","kind":"post","url":"https://x.com/patchkun_jp/status/2117753694645043528","author":"patchkun_jp","author_name":"パッチくん🐾WordPressの見張り係","avatar_url":"https://pbs.twimg.com/profile_images/2086341445007622144/mJrl3Nh9_bigger.jpg","text":"WordPress本体の脆弱性（CVE-2026-119977）、1週間見張ってきて「やっぱりきたか...」という気持ち。\n\nここまでの流れ👇️\n10/28 修正版7.1.4を公開\n10/28〜 攻撃の試み（Wordfence・21時間で18,500件超）\n10/31 CVE番号が付く（10点満点で8.1）\n11/3","engagement":0,"posted_at":"2026-11-03T23:00:01.000Z"},{"source":"x","kind":"post","url":"https://x.com/__kokumoto/status/2117751251811324017","author":"__kokumoto","author_name":"kokumօtօ","avatar_url":"https://pbs.twimg.com/profile_images/1612504196720492544/T_-s-6OP_bigger.jpg","text":"米国サイバーセキュリティ・社会基盤安全保障庁(CISA)が既知の悪用された脆弱性カタログにWordPress CoreのCVE-2026-119977を追加。対処期限は3日後の11/6。ランサムウェアによる悪用は不知。 https://t.co/eeQPiuCk8c\n差分：https://t.co/lHdPpvBC3k","engagement":0,"posted_at":"2026-11-03T22:50:19.000Z"},{"source":"x","kind":"post","url":"https://x.com/InfoNewsCyber/status/2117748954695893008","author":"InfoNewsCyber","author_name":"InfoNewsCyber","avatar_url":"https://pbs.twimg.com/profile_images/2115575922317254656/dfCYo5kK_bigger.jpg","text":"⚠️ FAILLE CRITIQUE\n\nCVE-2026-119977 activement exploitée : WordPress Core – Condition de concurrence « Time-of-check Time-of-use » (TOCTOU)\n\n🔗 https://t.co/tgmu2zdLZS\n#WordPress #ZeroDay","engagement":0,"posted_at":"2026-11-03T22:41:11.000Z"},{"source":"x","kind":"post","url":"https://x.com/aldabrahq/status/2117748154871243240","author":"aldabrahq","author_name":"aldabra","avatar_url":"https://pbs.twimg.com/profile_images/2115293572916232192/w-ARz3vo_bigger.png","text":"UPDATE: CISA added the WordPress core-update RCE (CVE-2026-119977) to its exploited list.\n\nUpdating closes it but won't show if a site was hit during an earlier update.\n\nhttps://t.co/3nDW6ugwbR https://t.co/3v2e1xMzyg","engagement":0,"posted_at":"2026-11-03T22:38:00.000Z"},{"source":"x","kind":"post","url":"https://x.com/autechwire/status/2117746657882235245","author":"autechwire","author_name":"AuTechWire","avatar_url":"https://pbs.twimg.com/profile_images/2117735690980970496/zVBWa1Ug_bigger.jpg","text":"WordPress CVE-2026-119977 is now on CISA's exploited list: unauthenticated code execution during core updates (4.7–7.1.3). Fixed in 7.1.4 and backports for every branch. Patched isn't the same as clean, so check wp-content/upgrade and your logs.\nhttps://t.co/S78aBTpnjZ","engagement":0,"posted_at":"2026-11-03T22:32:03.000Z"},{"source":"bluesky","kind":"post","url":"https://bsky.app/profile/ninjaintelgroup.bsky.social/post/3mzgug36cqe2d","author":"ninjaintelgroup.bsky.social","author_name":null,"avatar_url":"https://cdn.bsky.app/img/avatar/plain/did:plc:cf4z2xiwuqcij7gfavdbw5l3/bafkreihn4bshe7omoypugij43x22jbmgkhnc3yj3457g7vdhkv7w2dibh4","text":"🚨 NEW on CISA KEV — exploited in the wild\nWordPress WordPress Core: WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability\nCVE-2026-119977 · patch by 2026-11-06\n🔗 https://ninjasignal.ninja/intel/cve/CVE-2026-119977\n#KEV #cybersecurity #infosec","engagement":0,"posted_at":"2026-11-03T22:15:02.000Z"},{"source":"x","kind":"post","url":"https://x.com/notCVE/status/2117739606720303302","author":"notCVE","author_name":"NotCVE","avatar_url":"https://pbs.twimg.com/profile_images/1654046700019892224/qFYLMWzI_bigger.jpg","text":"⚠️ ACTIVELY EXPLOITED — added to CISA KEV 2026-11-03\n\nCVE-2026-119977: WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability\n\nCVSS 8.1 · EPSS 0.6%\n\nDetails, versions & intel → https://t.co/X7SKSz5OjH https://t.co/Xqqlo2DhBR","engagement":0,"posted_at":"2026-11-03T22:04:02.000Z"},{"source":"bluesky","kind":"post","url":"https://bsky.app/profile/vulnidx-jp.bsky.social/post/3mzgtcf4rpx2y","author":"vulnidx-jp.bsky.social","author_name":"vuln.idx（自動投稿）","avatar_url":"https://cdn.bsky.app/img/avatar/plain/did:plc:ibrmyanforok3zbsb3az5zx5/bafkreif7o5em6qmn3cvty5k4l2bpzi6efrnwk3hg6jbcx24coorte7pnri","text":"【悪用確認】CVE-2026-119977\nWordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability\nWordPress Core\nCISA 追加 11/3・対応期限 11/6\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-119977\n#脆弱性 #KEV #WordPress","engagement":0,"posted_at":"2026-11-03T21:55:04.809Z"}],"exploit_repositories":[]}}