The Appointment Bookings for Zoom GoogleMeet and more – Wappointment plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to and including 2.7.6 via the appointmentkey parameter due to the appointment edit_key — the sole authorization token consumed by tryCancel() — being generated as a predictable, unsalted MD5 hash of only client_id (a sequential integer), start_at (a publicly observable appointment timestamp), and staff_id (a small enumerable integer), with no secret salt or random component, and the unauthenticated cancellation and rescheduling REST endpoints performing no ownership or identity verification beyond matching this reconstructible key. This makes it possible for unauthenticated attackers to compute valid edit_key values for appointments belonging to other users and cancel or reschedule those appointments arbitrarily. Exploitation requires the allow_cancellation or allow_rescheduling setting to be enabled on the site, both of which are common configurations for active booking deployments; an attacker can obtain the inputs needed to reconstruct a victim's key by booking their own appointment to observe their sequential client_id and correlating publicly visible appointment times and enumerable staff identifiers.
CVE-2026-9188
Score 5.3 from GitHub Security Advisory published 2026-07-02. a secondary CVSS source baseline 5.3; 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
- 5.3
- EG Score
- 5.3(high)
- EPSS
- 21.5%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 2, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.5/app/Models/Client.php#L39
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.5/app/Services/AppointmentNew.php#L190
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.5/app/Services/AppointmentNew.php#L347
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.5/app/Services/AppointmentNew.php#L40
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.6/app/Models/Client.php#L39
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.6/app/Services/AppointmentNew.php#L190
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.6/app/Services/AppointmentNew.php#L347
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wappointment/tags/2.7.6/app/Services/AppointmentNew.php#L40
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3546313%40wappointment&new=3546313%40wappointment&sfp_email=&sfph_mail=
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/07069f39-f892-4c19-8e0b-e5e17b1ffb21?source=cve
Vendor Advisories for CVE-2026-9188(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 15× in last 7d / 15× 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-06 16:52 UTCEG score recompute
- 2026-07-06 16:52 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 15:48 UTCEG score recompute
- 2026-07-05 15:48 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-04 14:44 UTCEG score recompute
- 2026-07-04 14:44 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 13:41 UTCEG score recompute
- 2026-07-03 13:41 UTCGHSA enrichment
- 2026-07-02 12:36 UTCEG score recompute
- 2026-07-02 12:36 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-9188?
When was CVE-2026-9188 disclosed?
Is CVE-2026-9188 actively exploited?
What is the CVSS score of CVE-2026-9188?
How do I remediate CVE-2026-9188?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9188
Is Your Infrastructure Affected by CVE-2026-9188?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.