CVE-2026-92561: Booking Calendar (WordPress plugin) · Cross-site Scripting
Affects Booking Calendar (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 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 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wpdevelopBooking Calendar | Affected
| Fixed in– |
AI-suggested
Since the vulnerability arises from the default disabled state of the nonce verification, enabling the 'booking_is_nonce_at_front_end' option to enforce nonce checks can mitigate exploitation. Users should monitor the vendor's advisory for any forthcoming official fixes. Until then, avoid exposing the vulnerable parameter to untrusted input and educate users about the risks of clicking suspicious links.
Description
The Booking Calendar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'options' parameter in all versions up to, and including, 11.8.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The nonce check is bypassed by default because the 'booking_is_nonce_at_front_end' option ships disabled, allowing unauthenticated requests to reach the vulnerable sink without any verification.
References
- wordfence.com/threat-intel/vulnerabilities/id/e8645b58-6b2a-4659-a002-d622453bea42?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/booking/tags/11.8.2/core/timeline/v2/wpbc-class-timeline_v2.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/booking/tags/11.8.2/core/lib/wpbc-ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/booking/tags/11.8.2/core/timeline/v2/wpbc-class-timeline_v2.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/booking/tags/11.8.2/core/timeline/v2/wpbc-class-timeline_v2.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3699185%40booking&new=3699185%40booking (opens in a new tab)