Booking Agent Broken Access Control in QuickCal - Appointment Booking Calendar for WordPress <= 1.0.16 versions.
CVE-2026-27377
Score 6.7 from GitHub Security Advisory published 2026-07-23. a secondary CVSS source baseline 6.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.7
- EG Score
- 6.7(high)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
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 computedSeverity67% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (1)
Auto-updated Jul 23, 2026Broken Access Control in WordPress QuickCal - Appointment Booking Calendar for WordPress Plugin - Patchstack
https://patchstack.com/database/wordpress/plugin/quickcal/vulnerability/wordpress-quickcal-appointment-booking-calendar-for-wordpress-plugin-1-0-16-broken-access-control-vulnerability?_s_id=cveVendor Advisories for CVE-2026-27377(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 19× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-31 14:53 UTCGHSA enrichment
- 2026-07-30 17:00 UTCEG score recompute
- 2026-07-30 16:59 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 19:03 UTCGHSA enrichment
- 2026-07-28 21:10 UTCEG score recompute
- 2026-07-28 21:10 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 23:18 UTCEG score recompute
- 2026-07-27 23:17 UTCGHSA enrichment
- 2026-07-27 01:08 UTCEG score recompute
- 2026-07-27 01:08 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:15 UTCEG score recompute
- 2026-07-26 03:15 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 11:48 UTCEG score recompute
- 2026-07-23 11:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-27377?
When was CVE-2026-27377 disclosed?
Is CVE-2026-27377 actively exploited?
What is the CVSS score of CVE-2026-27377?
How do I remediate CVE-2026-27377?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-27377
Is Your Infrastructure Affected by CVE-2026-27377?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.