CVE-2026-6286

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. A secondary CVSS source baseline 7.2; 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
7.2EG
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.6%CVSS: 7.2Exploit: 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 melograno Booking for Appointments and Events Calendar – Amelia versions up to and including 2.2 as affected. No release containing a fix is confirmed on record.

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Stored Cross-Site Scripting via customer name fields in versions up to and including 2.2. This is due to an authentication bypass where the AddBookingCommand explicitly skips nonce verification (Command.php line 186), allowing unauthenticated users to submit booking data. While the plugin applies sanitize_text_field() to customer firstName and lastName fields (BookingApplicationService.php lines 302-308), this function only removes HTML tags and preserves special characters including double quotes. The vulnerability manifests in the administrative Calendar view where a FullCalendar eventContent callback interpolates customer names directly into JavaScript template literals (redesign/dist/index.js line 199) and renders them via innerHTML without proper HTML entity encoding. Because double quotes are preserved, an attacker can inject payloads like '" onmouseover="alert(document.cookie)"' to break out of the title attribute and inject malicious event handlers. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute when an administrator accesses the Calendar page and hovers over the malicious appointment.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.6% × 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 partial (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.6%
EPSS %ILE
48th
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 partial (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)14 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 partial (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

August 28, 2026

Last Modified

August 28, 2026

Vendor Advisories for CVE-2026-6286(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 21× in last 7d / 102× 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 171 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 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-6286?
CVE-2026-6286 is a high-severity vulnerability; its CVE record was published on August 28, 2026. The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Stored Cross-Site Scripting via customer name fields in versions up to and including 2.2. This is due to an authentication bypass where the AddBookingCommand explicitly skips nonce verification…
When was the CVE record for CVE-2026-6286 published?
The CVE record for CVE-2026-6286 was published on August 28, 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 August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-6286 actively exploited?
CVE-2026-6286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6286?
CVE-2026-6286 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6286?
No fix for CVE-2026-6286 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 melograno Booking for Appointments and Events Calendar – Amelia versions up to and including 2.2 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-6286 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-6286?

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