Stuart Neal
Director of Operations at Nextgen Marketing
We have worked with Vitalli and his team for well over a year now and will continue to do so in the future.
Having the confidence in an agency that allowed us to scale up and down development resources, as and when needed, has really made a positive difference to our agency.
Home / Blog / News / 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.
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.
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.
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.
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