CVE-2026-123128: GemBooking (WordPress plugin) · Race Condition
Affects GemBooking (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 1.7.1 soon.
Data as of 9 Nov 2026, 06:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.7.1
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade GemBooking (WordPress plugin) to 1.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GemBooking | Affected
| Fixed in
|
AI-suggested
Upgrade the GemBooking plugin to version 1.7.1 or later, where this race condition vulnerability has been fixed. No other mitigation is required once the plugin is updated.
Description
A race condition vulnerability exists in the GemBooking WordPress plugin versions before 1.7.1. This flaw allows unauthenticated users to send simultaneous booking requests that are not properly serialized per team member, resulting in overlapping confirmed bookings for the same team member across different bookable items.