Koffei

CVE-2026-119977

🔴 High In CISA KEV

WordPress Core (WordPress Foundation). Four preconditions must all hold, which is what the AC:H reflects: an affected version ; core updates applied through the WordPress updater ; wp-content/upgrade/ web-accessible and executing PHP ; and the attacker reaching the staged files between unpacking and cleanup. No account, no privileges and no user interaction are needed · 4.7.0 through 7.1.3, written in the record as 25 separate branch ranges (4.7.0 up to and including 4.7.38, 4.8.0 up to and including 4.8.33, and so on to 7.1.0 up to and including 7.1.3)

CVSS (Koffei note)
8.1
CVSS (v3.1, CVE List)
8.1
EPSS (2026-11-18)
1.586%
76.09th percentile
CISA KEV
2026-11-03
due 2026-11-06

Exploitation

Yes — CISA KEV since 03/11/2026 (SSVC 03/11/2026: exploitation active, automatable no, technical impact total). What was actually observed is attempts at scale rather than compromise, and the distinction matters here: Wordfence blocked 62,969 requests against this flaw in the 24 hours to 30/10/2026, with two of the largest sources polling small groups of sites for roughly 14.5 hours and others cycling staging-directory and version-name variations. No successful compromise has been reported by Wordfence, by WordPress or in press coverage. The race window lasted only seconds in Wordfence's lab, which is why the attack is built on repeated polling and why SSVC rates it not automatable. Timeline: disclosed 28/10/2026, advisory GHSA-4w3m-c66w-69mg on 29/10/2026, CVE record 31/10/2026, KEV 03/11/2026. Found by Umut Bayram Rechecked on 09/11/2026: the KEV listing of 03/11/2026 is 6 days old, well inside the window, so this stays 🔴, and EPSS has risen again. Existing PoC (not opened), recorded from the proof-of-concept list supplied on 09/11/2026. cyberveille still has no alert for this id

Timeline

  1. 31/10/2026CVE record published (CVE List)
  2. 03/11/2026Added to the CISA KEV catalogue
  3. 04/11/2026WordPress Core — CISA confirms active exploitation, CVSS 8.1
  4. 05/11/2026WordPress Core actively exploited during upgrades
  5. 06/11/2026CISA deadline for US federal agencies
  6. 09/11/2026WordPress Core "WP2Shell" unauthenticated RCE

Risk

8.1 High (v3.1, Wordfence as CNA) — AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS 1.157% (67.28th percentile, scored 08/11/2026, up from 1.020% and from 0.600% before that, so it has risen at every recheck) — and WordPress itself rates the same race condition Low, so three parties disagree on how bad this is: WordPress says Low, Wordfence says 8.1 High, CISA put it in KEV (CWE-367 time-of-check time-of-use race : core updates are staged in a predictable, web-served directory named from the package filename, such as wp-content/upgrade/wordpress-7.1.4. wp-admin/setup-config.php refuses to run only when wp-config.php already exists, and release packages ship wp-config-sample.php instead, so the staged installer runs. An unauthenticated attacker submits database settings, the wizard writes a wp-config.php into the staging tree, and the staged admin screens, which include plugin and theme upload, give PHP execution. Before 7.1.4 the copy step skipped only wp-content and wp-includes/version.php, so the attacker's wp-config.php could be copied to the site root and execute on every request afterwards)

Fix

Yes — fix commit b625b2d49c6a in 7.1.4 of 28/10/2026, backported to every branch eligible for security fixes, back to 4.7: 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31, 4.9.35, 4.8.34 and 4.7.39 (WordPress 7.1.4, which carries 13 security fixes in all ; sites with automatic background updates enabled start the update themselves). Two things to carry into practice. Applying the update is itself exposed for the seconds it takes, so on an unpatched site block web access to /wp-content/upgrade/ first: nginx location ^~ /wp-content/upgrade/ { return 403; } or Apache RedirectMatch 403 ^/wp-content/upgrade/. The index.php that WordPress writes there stops directory listing only, not direct requests. To hunt retrospectively, search access logs for requests to PHP files under wp-content/upgrade/, above all setup-config.php, decoding percent-encoded paths first, and run find wp-content/upgrade -name "*.php" : the only expected file is an index.php containing // Silence is golden., so any other PHP file there, and a wp-config.php especially, needs investigation

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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-367