WordPress core landed on the US actively-exploited list four times in 2026. It had never been there before

CISA’s Known Exploited Vulnerabilities catalog is a narrow list by design: a flaw only gets added once the US cybersecurity agency has evidence it is being exploited in the wild, not merely that it exists. WordPress core entered that list for the first time in July 2026, and as of the 18 November catalog release it is on there four times. Every one of those four entries was added this year. The catalog’s only previous WordPress entries, all from November 2021, were plugins — File Manager, Duplicator and Social Warfare — never core itself. Four confirmed-exploited core flaws in five months changes the arithmetic behind a patch window measured in days rather than quarters.

The four entries

  • CVE-2026-60137 and CVE-2026-63030, both added 21 July 2026. An SQL injection and an interpretation conflict that chain together — CISA’s own note on the first says the pair allows “an unauthenticated attacker to gain remote code execution on default WordPress installations”. Fixed in WordPress 7.0.2. The remediation deadline on the interpretation conflict was 24 July, three days after it was listed
  • CVE-2026-87902, added 25 September 2026. A remote file inclusion flaw letting an unauthenticated attacker make page-template resolution include a chosen readable local `.php` file outside the active theme directories, reaching remote code execution. Remediation deadline: 28 September, three days
  • CVE-2026-119977, added 3 November 2026. A time-of-check time-of-use race condition allowing unauthenticated code execution during the upgrade window itself, caused by predictable, web-accessible staging paths used during full-package core upgrades. Fixed in WordPress 7.1.4. Remediation deadline: 6 November, three days

Three of the four also carry CISA’s forensic triage requirement, which is the agency’s way of saying that patching alone may not be sufficient — if a site was exposed, you are also meant to look for whether anything already happened.

What is actually new here

Two things, and it is worth separating them.

The first is that the exploitation is confirmed rather than theoretical. A KEV listing is not a severity score; it is an observation. Every one of these four was being used against real sites before it was listed.

The second is the compression of the timeline. Three days is the typical deadline attached to these entries. That window is set for US federal agencies under binding directive, not for a web design agency in Europe — but it is a reasonable read on how fast the people exploiting these move. The TOCTOU race condition is the sharpest example: it attacks the upgrade process, meaning the vulnerable moment is the one where a site is doing the right thing.

What this looks like on a client portfolio

  • Every one of these four is patched in a current WordPress version, and all four were fixed by core releases that shipped before the KEV listing. There is no outstanding unpatched issue in this list — the whole exposure is the gap between release and installation
  • An unauthenticated remote code execution path on a default installation means there is no “but our client sites are low-profile” argument available. Nobody is being targeted; ranges are being scanned
  • If you manage sites that sit on deliberately delayed updates — a staging-then-production policy, a client who insists on approving changes, a site nobody wants to touch — these four are the argument for carving out a security-release exception from that policy
  • Three of the four want you to check for compromise, not just patch. For any site that spent weeks unpatched during these windows, a file integrity check and a look at admin accounts is the honest minimum

Some perspective is fair here too. WordPress appearing on this list is partly a function of its share of the web and partly a function of more people — and more automated tooling — looking hard at it this year. The core security team’s response times on all four were good, and the releases were out ahead of the listings. The number that matters for an agency is not how many flaws were found; it is how many days your clients’ sites sat on the old version after each fix shipped.

What this means for Codelibry clients

If your site is on one of our maintenance plans, all four of these were applied as the core releases came out, and each one is already recorded in the monthly maintenance report for the month it landed in — you can look back and see the dates. Nothing here needs your attention. If you are not on a plan, this is the clearest version of the case for one: four separate occasions this year where the difference between a safe site and a compromised one was how quickly someone pressed update.

Source: CISA

Vitalii Omelchenko
Founder at Codelibry and WordPress enthusiast. Helping digital agencies to protect their margins and do better at website delivery.Need help with wordpress builds? Book a call using the Contact page
our Blog

Explore our Latest Insights

PHP shipped 18 CVEs worth of fixes this week. Two of them reach an ordinary WordPress site
News
November 20, 2026
Two critical NGINX HTTP/2 flaws can reach code execution. Updating WordPress will not help
News
November 20, 2026
WordPress 7.1.5 ships 20 security fixes, including an unauthenticated path to RCE
News
November 19, 2026
whatsapp icon