WP Hotel Booking <= 2.3.2 - Reflected Cross-Site Scripting via 'check_in_date' Parameter
The WP Hotel Booking plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'check_in_date' parameter in all versions up to, and including, 2.3.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.
Browse WordPress security risksQuick answer
WP Hotel Booking 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
- up to and including 2.3.2
Fixed versions
- 2.3.3
How to fix it
WP Hotel Booking is affected by CVE-2026-15094, an unauthenticated reflected cross-site scripting flaw in check_in_date. A malicious booking link can run script in the browser of a user who opens it. Update WP Hotel Booking to 2.3.3 or a newer vendor-supported patched release. Prioritize exposed production systems and accounts that can reach the affected feature.
- Inventory every WP Hotel Booking deployment, version, exposed endpoint, environment, and owner.
- Confirm the installed release is not an affected version up to and including 2.3.2.
- Update WP Hotel Booking to 2.3.3 or a newer vendor-supported patched release.
- Until the update is complete, disable affected booking pages or enforce a strict date format for check_in_date at the edge.
- Review requests and referrers for encoded scripts or event handlers in check_in_date.
- Revoke exposed sessions and inspect booking, customer, and administrator changes made after a malicious link was opened.
- Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm WP Hotel Booking is on the patched version or mitigation stated above and record the exact deployed version.
- Confirm check_in_date accepts only a valid date and is safely escaped in every response.
- Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
- Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
- Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-15094.
Related categories
Related security risks
More published guidance from the same primary category.
WP Hotel Booking <= 2.3.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'widget_search' Shortcode Attribute
Updated July 24, 2026
mediumWP Hotel Booking <= 2.3.1 - Reflected Cross-Site Scripting via 'check_in_date' and 'check_out_date' Parameters
Updated July 13, 2026
mediumWP Hotel Booking <= 2.3.1 - Unauthenticated Insufficient Verification of Data Authenticity to Payment Bypass via PayPal IPN Handler
Updated July 13, 2026
Trusted references
FAQ
What is affected by CVE-2026-15094?
WP Hotel Booking versions listed as affected should be reviewed: up to and including 2.3.2.
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.