The Booking Package WordPress plugin before 1.7.33 does not restrict who can trigger its booking verification-code
Source GCVE Database
Not known to be exploited : upgrade to 1.7.33 when convenient.
Data as of 28 Oct 2026, 07:28 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.7.33
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Booking Package (WordPress plugin) to 1.7.33.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Booking Package | Affected
| Fixed in
|
AI-suggested
Upgrade the Booking Package WordPress plugin to version 1.7.33 or later, where this issue is fixed. No other mitigation is indicated by the available data.
Description
The Booking Package WordPress plugin versions before 1.7.33 allow unauthenticated users to trigger booking verification-code emails to arbitrary recipients without restriction or server-side binding. This can lead to abuse of the email functionality to send unsolicited templated emails.