Threadlinqs IntelligenceStart free

Vendor1 product tracked

WordPress vulnerabilities & exploitation

1 in CISA KEV4 with public exploit

As of 2026-11-07, Threadlinqs tracks 5 WordPress CVEs, 1 in the CISA Known Exploited Vulnerabilities catalog, linked to 46 tracked threat campaigns and 12 named threat actors.

CVEs
5Since 2026
CISA KEV
120% of CVEs
Critical
1CVSS v3 9.0+
Avg CVSS
8.3/10Max 9.8
Threats
46Linked campaigns
Actors
12Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 5 WordPress CVEs published between and . The busiest month was 2026-07 (2 new CVEs). 1 of them (20%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 5 of 5 tracked WordPress CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 5 CVEs; 1 distinct WordPress product is affected. The most frequently affected:

  • WordPress 5 CVEs

Threat activity

46 tracked threat campaigns reference WordPress products or exploit WordPress CVEs; the 25 most recent are listed.

Threat actors targeting WordPress

Named threat actors attributed to campaigns that involve WordPress products or CVEs, with the number of linked campaigns:

How to prioritise WordPress patching

This order follows the data Threadlinqs holds for WordPress, not a generic severity checklist:

  • 1 of 5 WordPress CVEs (20%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2026-63030.
  • Outside KEV, the highest EPSS scores are CVE-2026-65640 (1.9%).
  • 1 CVE scores Critical and 3 High on CVSS v3 (maximum 9.8, average 8.3); sequence these after KEV and high-EPSS items.
  • 4 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-07 and refresh daily.