CVE-2026-123131VulnerabilityPublished 9 Nov 2026

The GemBooking WordPress plugin before 1.7.1 does not properly verify that a REST request is addressed to its own

Source GCVE Database

Compare

Authoritative record:CVE-2026-123131· 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

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-frjm-xwcq-24jh

What to do

Upgrade GemBooking (WordPress plugin) to 1.7.1.

Affected software

Product	Affected	Fixed in
GemBooking	Affected <1.7.1	Fixed in 1.7.1

AI-suggested

Upgrade the GemBooking WordPress plugin to version 1.7.1 or later, where this issue has been fixed. No other mitigation or workaround is indicated.

Description

The GemBooking WordPress plugin versions before 1.7.1 contain a vulnerability where REST requests are not properly verified to belong to the plugin's own routes. This flaw allows users assigned the Staff role to temporarily gain administrative capabilities, enabling them to delete arbitrary posts and modify site settings.

Impact

Users with the Staff role in affected versions can exploit this vulnerability to gain temporary administrative capabilities. This enables them to delete any posts on the site and modify the site's settings, potentially leading to content loss and unauthorized configuration changes.

Summary

The GemBooking WordPress plugin prior to version 1.7.1 fails to properly verify that incoming REST API requests are targeted at its own routes before temporarily elevating Staff users to administrative privileges. This improper verification leads to an authorization bypass, allowing Staff role users to perform privileged actions such as deleting arbitrary posts and updating site-wide settings.

References

Community reviews

Loading reviews…