CVE-2026-107645

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-10. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The Blocksy Companion plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 2.1.58 This is due to the implement_user_registration() AJAX handler explicitly disabling Dokan's vendor-registration nonce check (via add_filter('dokan_register_nonce_check', '__return_false')) and then trusting an attacker-supplied $_POST['role'] value when invoking wc_create_new_customer() and wc_set_customer_auth_cookie(). This makes it possible for unauthenticated attackers to elevate their privileges to a Dokan 'seller' (vendor) account — including sites where the Dokan vendor signup is explicitly turned off — and to be auto-authenticated into that account, which grants publishing capabilities beyond those of a normal customer.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 10, 2026

Last Modified

October 11, 2026

References (5)

Vendor Advisories for CVE-2026-107645(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-12 01:18 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  2. 2026-10-11 21:31 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-11 20:14 UTCEG score recompute
  4. 2026-10-11 17:38 UTCEG score recompute
  5. 2026-10-11 17:38 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-11 17:02 UTCEG score recompute
  7. 2026-10-11 17:02 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-11 14:20 UTCEG score recompute
  9. 2026-10-11 14:20 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-11 10:33 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-11 06:45 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-11 02:58 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-10 23:11 UTCEG score recompute
  15. 2026-10-10 23:11 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-10 19:26 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-10 15:40 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-10 11:53 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-10 08:07 UTCEG score recompute
  21. 2026-10-10 08:06 UTCGHSA enrichmentGHSA-w5h9-m5j6-5394 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-10 04:20 UTCEG score recompute
  23. 2026-10-10 03:45 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  24. 2026-10-10 03:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107645?
CVE-2026-107645 is a critical-severity vulnerability; its CVE record was published on October 10, 2026. The Blocksy Companion plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 2.1.58 This is due to the implementuserregistration() AJAX handler explicitly disabling Dokan's vendor-registration nonce check (via addfilter('dokanregisternoncecheck',…
When was the CVE record for CVE-2026-107645 published?
The CVE record for CVE-2026-107645 was published on October 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 11, 2026; the record at its source may have been updated since.
Is CVE-2026-107645 actively exploited?
CVE-2026-107645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107645?
CVE-2026-107645 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107645?
No fix for CVE-2026-107645 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-107645 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-107645

Explore →

Is Your Infrastructure Affected by CVE-2026-107645?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs