GEMBOOKING · CVE-2026-123128 · Package
NO FIX YET · SEE WHAT TO DO
The GemBooking WordPress plugin before 1.7.1 does not serialise concurrent booking requests for the same team member. An unauthenticated visitor sending simultaneous requests can get overlapping confirmed bookings for one team member across different bookable items.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the GemBooking WordPress plugin before 1.7.1 that take bookings for team members. The risk is double-booking, not code execution. Sites without this plugin or already on 1.7.1 or later are not affected.
Not affected if plugin-at-1.7.1-or-later, plugin-not-installed
Who cares booking-sites, gembooking, wordpress
1.7.1 or later.The GemBooking WordPress plugin before 1.7.1 does not serialise concurrent booking requests per team member, allowing unauthenticated users to create overlapping confirmed bookings for the same team member across different bookable items by sending simultaneous requests.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.