CVE-2026-15011

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-23. 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.0%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 emarket-design Customer Support Ticket System & Helpdesk versions up to and including 6.0.5 as affected. No release containing a fix is confirmed on record.

The Customer Support Ticket System & Helpdesk plugin for WordPress is vulnerable to Code Injection via the 'path' parameter in all versions up to, and including, 6.0.5 due to the use of dynamic function invocation on an attacker-controlled value with insufficient validation. This makes it possible for unauthenticated attackers to invoke arbitrary parameterless PHP functions, which can be used to disrupt site functionality or expose sensitive information. The required nonce is publicly emitted via wp_localize_script whenever the plugin's [emd_form] shortcode is rendered on any public-facing page, making the endpoint reachable by unauthenticated visitors without any prior authentication or privilege.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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.0%
EPSS %ILE
60th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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 23, 2026

Last Modified

July 23, 2026

Vendor Advisories for CVE-2026-15011(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 22× in last 7d / 65× 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 430 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 330 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-15011?
CVE-2026-15011 is a critical-severity vulnerability; its CVE record was published on July 23, 2026. The Customer Support Ticket System & Helpdesk plugin for WordPress is vulnerable to Code Injection via the 'path' parameter in all versions up to, and including, 6.0.5 due to the use of dynamic function invocation on an attacker-controlled value with insufficient validation. This makes it possible…
When was the CVE record for CVE-2026-15011 published?
The CVE record for CVE-2026-15011 was published on July 23, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-15011 actively exploited?
CVE-2026-15011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15011?
CVE-2026-15011 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-15011?
No fix for CVE-2026-15011 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 emarket-design Customer Support Ticket System & Helpdesk versions up to and including 6.0.5 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15011 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15011?

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