Skip to main content
CVE-2026-123128VulnerabilityPublished

The GemBooking WordPress plugin before 1.7.1 does not serialise concurrent booking requests per team member, allowing

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123128· High

Not known to be exploited : upgrade to 1.7.1 soon.

Data as of 9 Nov 2026, 10:22 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GemBookingAffected
  • <1.7.1
Fixed in
  • 1.7.1

AI-suggested

A fixed version 1.7.1 or later of the GemBooking plugin addresses this issue by properly serializing concurrent booking requests. Users should upgrade to version 1.7.1 or later to remediate this vulnerability. No other mitigation guidance is provided.

Description

The GemBooking WordPress plugin versions prior to 1.7.1 have a concurrency control flaw that allows unauthenticated users to create overlapping confirmed bookings for the same team member by sending simultaneous booking requests. This occurs because the plugin does not serialize concurrent booking requests per team member, potentially leading to booking conflicts.

References

Community reviews

Loading reviews…