Easy!Appointments through 1.6.0 contains an authorization bypass vulnerability in Booking::register() that allows unauthenticated attackers to modify any appointment by supplying an appointment id without its hash. Attackers can enumerate sequential appointment ids with a self-asserted manage_mode flag to rewrite appointment details, rebind them to attacker-controlled customers, and obtain management hashes for rescheduling or cancellation.
CVE-2026-108758
HIGHPre-NVD 8.28.2Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-11. A secondary CVSS source baseline 8.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.2Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHhigh confidence
- EG Risk
- 37EG Risk 37/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)Severity82% × 45%The EG Score, 8.2 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 11, 2026
Last Modified
October 11, 2026
Advisory Details (5)
Auto-updated Oct 11, 2026Patch available. Sources: github_commit.
Web page
Easy!Appointments through 1.6.0 Authorization Bypass via booking/register Endpoint | Advisories | VulnCheck
https://www.vulncheck.com/advisories/easy-appointments-through-1.6.0-authorization-bypass-via-booking-register-endpointWeb page
GitHub - alextselegidis/easyappointments: :date: Easy!Appointments - Self Hosted Appointment Scheduler · GitHub
https://github.com/alextselegidis/easyappointmentsGitHub commit Patch Available
commit 09c6fb30b6aa (alextselegidis/easyappointments)
Patch available: alextselegidis/easyappointments 1.6.1-alpha.1 (contains commit 09c6fb30b6aa)
https://github.com/alextselegidis/easyappointments/commit/09c6fb30b6aac0830a820d6bec3d2eb241daf150Web page
easyappointments/application/controllers/Booking.php at 4bc7ecd51f3dade8e041558f2c23dda65bd6c43e · alextselegidis/easyappointments · GitHub
https://github.com/alextselegidis/easyappointments/blob/4bc7ecd51f3dade8e041558f2c23dda65bd6c43e/application/controllers/Booking.php#L368-L587Web page
Easy!Appointments: unauthenticated appointment takeover and customer PII overwrite via a client-supplied id in booking/register - HackMD
https://hackmd.io/@haind/easyappointments-booking-register-appointment-takeoverVendor Advisories for CVE-2026-108758(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 8× in last 7d / 8× 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.
- 2026-10-12 02:22 UTCEG score recompute
- 2026-10-12 02:22 UTCGHSA enrichmentGHSA-q8ph-7hq3-m5wq · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-11 20:13 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 14:59 UTCEG score recompute
- 2026-10-11 13:19 UTCEG score recompute
- 2026-10-11 12:37 UTCEG score recomputeFirst assessed: 8.2 HIGH
- 2026-10-11 12:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-108758?
CVE-2026-108758 is a high-severity vulnerability; its CVE record was published on October 11, 2026. Easy!Appointments through 1.6.0 contains an authorization bypass vulnerability in Booking::register() that allows unauthenticated attackers to modify any appointment by supplying an appointment id without its hash. Attackers can enumerate sequential appointment ids with a self-asserted manage_mode…
When was CVE-2026-108758 made public?
CVE-2026-108758 was made public on October 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 11, 2026. 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.
What is the CVSS score of CVE-2026-108758?
CVE-2026-108758 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108758?
A fix for CVE-2026-108758 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108758 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108758
Is Your Infrastructure Affected by CVE-2026-108758?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.