Booking Package <= 1.7.20 - Unauthenticated SQL Injection via 'email' Form Parameter
The Booking Package plugin for WordPress is vulnerable to generic SQL Injection via 'email' Form Parameter (form<N>) in all versions up to, and including, 1.7.20 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable REST API endpoint /wp-json/booking-package/v1/request is registered with permission_callback: __return_true and wp_magic_quotes does not apply to REST-sourced $_POST values, meaning single quotes in the payload reach the SQL sink intact without any authentication requirement. The impact of this is severely limited as the vulnerable parameter goes through is_email.
Quick answer
Booking Package should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-1.7.20
Fixed versions
- 1.7.21
How to fix it
Booking Package is affected by CVE-2026-15335, a SQL injection issue in versions up to 1.7.20. Wordfence lists the official remediation as updating to version 1.7.21, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has Booking Package installed, including production, staging, multisite, client, and WooCommerce environments.
- Confirm the installed Booking Package version and compare it with the affected range from the Wordfence advisory.
- Update Booking Package to version 1.7.21, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable Booking Package or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review database logs, application logs, suspicious queries, exported records, user accounts, orders, bookings, form entries, and configuration changes for evidence of data access or tampering.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running Booking Package version is version 1.7.21 or newer, and record the patched version in the remediation ticket.
- Verify malicious SQL payloads are rejected or parameterized and no longer change query structure or expose database errors.
- Review web server, WordPress, security plugin, WAF, database, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-15335?
Booking Package versions listed as affected should be reviewed: *-1.7.20.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.