---
id: "CVE-2026-105997"
kind: "vulnerability"
aliases: ["CVE-2026-105997"]
title: "Booking Package WordPress plugin lets anyone trigger verification emails"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["booking-package", "package", "self-hosted", "wordpress"]
not_affected_if: ["feature-disabled", "plugin-updated"]
published_at: "2026-10-28T06:16:32+00:00"
first_seen_at: "2026-10-28T06:31:26+00:00"
updated_at: "2026-10-28T06:32:52+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105997", "first_seen_at": "2026-10-28T06:31:26+00:00"}]
---

# Booking Package WordPress plugin lets anyone trigger verification emails

The Booking Package WordPress plugin before 1.7.33 does not check who can request booking verification-code emails. An unauthenticated visitor can make the site send templated verification emails to any address they choose.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of the Booking Package plugin in the WordPress admin under Plugins, or in `wp-content/plugins/` for the plugin's main file header.
- Confirm whether the booking verification-code feature is enabled on the site.

## Fix

- Update the Booking Package WordPress plugin to `1.7.33` or later.
- Until updated, disable the booking verification-code feature if it is not needed.

## Timeline

- 2026-10-28T06:31:26+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-105997

## From the sources

The Booking Package WordPress plugin before 1.7.33 does not restrict who can trigger its booking verification-code emails nor bind the recipient to server-side state, allowing unauthenticated users to make the site send templated verification-code emails to arbitrary recipients.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_