EN
FRENDEESAR
34 vulnerabilities published on November 21, 2026

34 vulnerabilities published on November 21, 2026

Published and updated on 22 November 2026 · 4 min read · by
Sommaire(3)MasquerAfficher
  1. Quelles failles du 21 novembre touchent vraiment des sites ?
  2. Que doit retenir une entreprise ?
  3. FAQ

Of the 34 vulnerabilities we published on November 21, 2026, 21 affect a component we have actually seen in service on at least one site, and 13 concern no software present in what we measure. The most widespread is a WordPress theme, installed on 4,906 domains in our dataset. This breakdown is the only information that matters to an executive: a published vulnerability is not a vulnerability that concerns them.

The rest of this text gives the detail component by component, what this figure does not say, and what a company should take away from it. The full advisories, with the corrected version and the remediation steps, are in our vulnerability catalogue.

Which November 21 vulnerabilities actually affect websites?

Ranking by number of sites does not look like ranking by score, and that is the whole point of cross-referencing. Here are the components we actually read on at least one site, with the number of times they appear in our fleet and, above all, the number of sites still running a version that the vulnerability reaches.

Vulnerabilities of November 21, 2026, measured on November 22, 2026
ComponentCVEsSites
concerned
Of which
vulnerable
oceanwpCVE-2026-13413614,9124,373
SpectraCVE-2026-12906311,7520
Quiz MakerCVE-2026-12903318536
zephyrCVE-2026-95825 CVE-2026-95826 CVE-2026-9582734738
Appointment Hour BookingCVE-2026-12905511613
Element Pack Elementor AddonsCVE-2026-130601 CVE-2026-130602220
@qwik.dev/routerCVE-2026-134169122
WP Job PortalCVE-2026-129037122
Creo Elements/Direct LicenseCVE-2024-3951 CVE-2024-6071210
Revolut Gateway for WooCommerceCVE-2023-52224 CVE-2024-8678211
MarketingCVE-2024-21169110
Product DesignerCVE-2024-38726111
RecipePress ReloadedCVE-2024-11414111
Sign In With GoogleCVE-2024-11015111
Smart Countdown FXCVE-2025-25117111
Smart Shopify ProductCVE-2024-56031111
solidCVE-2025-27109111

The table reads from top to bottom. The "affected sites" column counts the domains where we detected the component, regardless of its version. The "of which vulnerable version" column keeps only those whose number falls within a range declared by the vulnerability. On OceanWP, the gap between the two columns is the good news of the day: the theme is everywhere, but the vast majority of sites already have the fixed version. The table was reviewed on November 22, on a larger set than that of the 21st: on the day of publication, 21 vulnerabilities were tied to a detected component, the next day there are 22, and OceanWP went from 4,906 to 4,912 domains. Every figure on this site carries its date, and that is precisely what makes it verifiable.

Conversely, the three highest scores of the day affect almost no one in what we measure: 10.0 for a PTC Creo license server, 9.8 for a "Sign In With Google" extension and 9.8 for Apache Solr, a search component that we found on no domain in the measured estate. A company that sorts its alerts by score is therefore working on the wrong ones.

The details of each entry give the exact version range and the remediation, for example for CVE-2026-134169, a denial of service in Qwik City fixed in 1.20.3.

What should a company remember?

Three steps, in this order. The first determines the other two: without the list of what your site runs, there is nothing to sort, and nothing to fix.

  • Know what your site is running. Without this list, no alert is actionable: you cannot tell whether a vulnerability affects you.
  • Sort alerts by component present in your environment, not by score. A vulnerability rated 4.8 in a theme you use takes priority over a vulnerability rated 10.0 in software you do not have.
  • Fix in the order of what is exposed to the Internet, starting with the modules your visitors load without knowing it, such as a theme or a form builder.

A flaw in a theme is fixed with an update, usually in under ten minutes. The time spent deciding which one to fix first often costs more than the fix itself. Our pentest guide for 2026 details how to then verify that the fix is actually in place, version in hand.

FAQ

Is a vulnerability with no affected site in our estate harmless?

No. It only says that we did not find it on the sites we read. A component can be present without being detectable, removed from public space, hidden by a firewall, modified by the host. The figure describes our reading, not the immunity of your site.

Why sort by component and not by score?

The score measures the severity of a vulnerability in itself, not the probability that it affects you. A vulnerability rated 4.8 on a theme you actually use takes priority over a vulnerability rated 10.0 in software you do not have. The score is used to decide between two vulnerabilities that affect you, not to decide whether they affect you.

How can I find out what my site is running?

You need to read the site's response, not query its host. The page tags, script files and headers reveal the software, the theme and often the version. Our home page performs this reading for a domain, and each catalogue entry lists the affected versions.

Will these figures be updated?

Yes. The fleet is continuously probed, and the counters on the home page track the actual measurement. This text carries its date: the 34 vulnerabilities of 21 November and the 276,971 domains for which we know a component are a snapshot, not a permanent state.

wordpresscomposantsméthode

À lire aussi