CVE-2026-108123

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-17. A secondary CVSS source baseline 7.5; 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

Also known asEUVD-2026-103228 (ENISA EUVD) · GHSA-2wvw-mp72-5fwj (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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: 7.5Exploit: 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 murgroland WP Booking System – Booking Calendar versions up to and including 2.1.0.3 as affected. No release containing a fix is confirmed on record.

The WP Booking System – Booking Calendar plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.1.0.3 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to read the stored notification email body of any booking by iterating booking_id and email_log_id, exposing customer PII including names, email addresses, phone numbers, messages, and booking dates intended to be visible only to administrators. This is exploitable by any Subscriber-level user because admin_init fires on profile.php, a wp-admin page accessible to all authenticated users.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 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
1.0%
EPSS %ILE
63rd
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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. 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: 14 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 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

October 17, 2026

Last Modified

October 19, 2026

References (6)

Vendor Advisories for CVE-2026-108123(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 10× in last 7d / 27× 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-30 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  2. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  3. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-27 18:08 UTCEG score recompute
  5. 2026-10-27 18:08 UTCGHSA enrichmentGHSA-2wvw-mp72-5fwj · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-25 14:54 UTCEG score recompute
  10. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-10-19 15:26 UTCEG score recompute
  17. 2026-10-19 15:26 UTCGHSA enrichmentGHSA-2wvw-mp72-5fwj · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-18 12:26 UTCEG score recompute
  20. 2026-10-18 12:26 UTCGHSA enrichmentGHSA-2wvw-mp72-5fwj · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-18 11:36 UTCEG score recompute
  22. 2026-10-18 11:36 UTCGHSA enrichmentGHSA-2wvw-mp72-5fwj · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-18 05:07 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-10-17 04:27 UTCEG score recompute
Show 2 more
  1. 2026-10-17 03:49 UTCEG score recomputeFirst assessed: 7.5 HIGH
  2. 2026-10-17 03:47 UTCMITRE cvelistV5first tracked

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-108123.yaml
    Recorded Oct 28, 2026

    WP Booking System <= 2.1.0.3 - Unauthenticated Email Log Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-108123?
CVE-2026-108123 is a high-severity vulnerability; its CVE record was published on October 17, 2026. The WP Booking System – Booking Calendar plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.1.0.3 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to…
When was the CVE record for CVE-2026-108123 published?
The CVE record for CVE-2026-108123 was published on October 17, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-108123 actively exploited?
CVE-2026-108123 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108123?
CVE-2026-108123 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108123?
No fix for CVE-2026-108123 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 murgroland WP Booking System – Booking Calendar versions up to and including 2.1.0.3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-108123 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-108123?

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

Book a Demo →Browse All CVEs