CVE-2026-15158

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
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: 1.1%CVSS: 9.8Exploit: 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 CVE record's CNA (Wordfence) lists creativethemeshq Blocksy Companion versions up to and including 2.1.46 as affected. No release containing a fix is confirmed on record.

The Blocksy Companion plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.1.46 via the save_attachments function. This is due to the Custom Fonts extension registering a wp_check_filetype_and_ext filter that approves any filename containing .woff2 or .ttf as a substring via strpos() rather than validating that those strings appear as the final extension via PATHINFO_EXTENSION — allowing double-extension filenames such as shell.woff2.php to pass MIME validation and be handled as permitted font files. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. This vulnerability is only exploitable when the premium version of the plugin (blocksy-companion-pro) is installed with both the WooCommerce Extra (Advanced Reviews) and Custom Fonts extensions active; the free blocksy-companion plugin does not contain the vulnerable code paths.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.1% × 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
1.1%
EPSS %ILE
63rd
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

July 9, 2026

Last Modified

July 9, 2026

References (3)

Vendor Advisories for CVE-2026-15158(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 14× in last 7d / 40× 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.

Showing the most recent 100 of 394 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 294 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  2. 2026-10-13 10:02 UTCEG score recompute
  3. 2026-10-13 10:02 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  5. 2026-10-12 16:32 UTCEG score recompute
  6. 2026-10-12 09:40 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-11 20:10 UTCEG score recompute
  8. 2026-10-11 17:22 UTCEG score recompute
  9. 2026-10-11 14:55 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  20. 2026-10-01 16:05 UTCEG score recompute
  21. 2026-10-01 16:05 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  23. 2026-09-29 15:20 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  25. 2026-09-28 11:06 UTCEG score recompute
Show 75 more
  1. 2026-09-28 11:06 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  4. 2026-09-24 11:41 UTCEG score recompute
  5. 2026-09-24 11:41 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-09-23 09:54 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-09-23 06:00 UTCEG score recompute
  8. 2026-09-23 06:00 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  10. 2026-09-18 10:09 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-09-18 05:38 UTCEG score recompute
  12. 2026-09-18 05:38 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  14. 2026-09-16 05:14 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  15. 2026-09-14 11:24 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-09-14 07:32 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-09-14 03:39 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-09-13 23:47 UTCEG score recompute
  19. 2026-09-13 23:47 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-09-13 16:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  21. 2026-09-13 16:43 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-09-13 12:13 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-09-13 08:20 UTCEG score recompute
  24. 2026-09-13 08:20 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-09-12 15:00 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  26. 2026-09-12 13:34 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-09-12 03:26 UTCEG score recompute
  28. 2026-09-12 03:26 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  30. 2026-09-11 09:36 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  31. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  32. 2026-09-08 22:00 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  33. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  34. 2026-09-06 14:00 UTCEG score recompute
  35. 2026-09-06 14:00 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  37. 2026-09-06 02:31 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-09-05 22:36 UTCEG score recompute
  39. 2026-09-05 22:36 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  41. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  42. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  43. 2026-08-31 00:29 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-08-30 20:36 UTCEG score recompute
  45. 2026-08-30 20:36 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  47. 2026-08-30 16:43 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-08-30 11:13 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-08-30 06:57 UTCEG score recompute
  50. 2026-08-30 06:57 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.1% · 61st percentile
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.1% · 61st percentile
  53. 2026-08-28 02:42 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-08-27 21:47 UTCEG score recompute
  55. 2026-08-27 21:47 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  57. 2026-08-27 01:12 UTCEG score recompute
  58. 2026-08-27 01:12 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  60. 2026-08-26 12:55 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-08-26 08:19 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-26 03:56 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-25 14:47 UTCEG score recompute
  64. 2026-08-25 14:47 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-25 13:48 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  66. 2026-08-25 10:07 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-25 04:08 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-25 00:15 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-24 20:22 UTCEG score recompute
  70. 2026-08-24 20:22 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-24 13:35 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-08-24 09:37 UTCEG score recompute
  73. 2026-08-24 09:37 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-08-24 03:59 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-23 23:05 UTCGHSA enrichmentGHSA-hhjp-58g7-3jr8 · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15158?
CVE-2026-15158 is a critical-severity vulnerability; its CVE record was published on July 9, 2026. The Blocksy Companion plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.1.46 via the saveattachments function. This is due to the Custom Fonts extension registering a wpcheckfiletypeandext filter that approves any filename containing .woff2 or .ttf…
When was the CVE record for CVE-2026-15158 published?
The CVE record for CVE-2026-15158 was published on July 9, 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 July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-15158 actively exploited?
CVE-2026-15158 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15158?
CVE-2026-15158 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15158?
No fix for CVE-2026-15158 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 CVE record's CNA (Wordfence) lists creativethemeshq Blocksy Companion versions up to and including 2.1.46 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15158 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15158?

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

Book a Demo →Browse All CVEs