WP Hotel Booking <= 2.3.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'widget_search' Shortcode Attribute
The WP Hotel Booking plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'widget_search' Shortcode Attribute in all versions up to, and including, 2.3.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable on browsers where access keys can be used as the payload is stored in a hidden attribute.
Browse WordPress security risksQuick answer
thimpress 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
- <= 2.3.2
- up to and including 2.3.2
Fixed versions
- 2.3.3
How to fix it
CVE-2026-15464 affects WP Hotel Booking and involves cross-site scripting. Successful exploitation may run attacker-controlled script in a trusted user's browser and expose session or application data. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade WP Hotel Booking to 2.3.3 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses WP Hotel Booking.
- Compare the installed version with the recorded affected range: <= 2.3.2, *-2.3.2.
- Upgrade WP Hotel Booking to 2.3.3 or a later vendor-supported fixed release.
- Until patched, disable the affected WP Hotel Booking feature or plugin and restrict its public and administrator endpoints.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to WP Hotel Booking; remove access that is not required.
- Review submissions, stored content, administrator activity, CSP reports, and web logs for script payloads or suspicious browser requests.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15464 in place.
- Use a safe regression test to confirm the affected cross-site scripting path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
WP Hotel Booking <= 2.3.2 - Reflected Cross-Site Scripting via 'check_in_date' Parameter
Updated July 19, 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-15464?
thimpress WP Hotel Booking versions listed as affected should be reviewed: <= 2.3.2, 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.
