mediumCVE-2026-11901

WP Hotel Booking <= 2.3.1 - Unauthenticated Insufficient Verification of Data Authenticity to Payment Bypass via PayPal IPN Handler

Q: What is affected by CVE-2026-11901?

WP Hotel Booking versions listed as affected should be reviewed: *-2.3.1.

Q: 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.

Q: 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.

Q: 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.

The WP Hotel Booking plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in all versions up to, and including, 2.3.1. This is due to the `web_hook_process_paypal_standard()` IPN handler selecting its PayPal validation endpoint from the attacker-controlled `$_REQUEST['test_ipn']` parameter, force-upgrading any `pending` transaction to `completed` when `test_ipn=1`, and omitting post-verification checks on `receiver_email`, `mc_currency`, and `txn_id` uniqueness after receiving a `VERIFIED` response from PayPal. This makes it possible for unauthenticated attackers to mark arbitrary hotel bookings as fully paid without submitting genuine payment to the merchant — either by routing IPN validation through PayPal's sandbox using a free sandbox account, or by replaying a previously verified IPN from a nominal payment to an attacker-controlled PayPal account. An attacker requires only a free PayPal sandbox account (or any PayPal account) to obtain a `VERIFIED` response; no site credentials or special configuration are needed.

ProductWP Hotel Booking

CVSS5.3

EPSSNot scored yet

UpdatedJuly 13, 2026

Quick 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

*-2.3.1

Fixed versions

2.3.2

How to fix it

WP Hotel Booking is affected by CVE-2026-11901, a WordPress plugin vulnerability issue in versions up to 2.3.1. Wordfence lists the official remediation as updating to version 2.3.2, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, 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 WP Hotel Booking installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
Confirm the installed WP Hotel Booking version and compare it with the affected range from the Wordfence advisory.
Update WP Hotel Booking to version 2.3.2, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable WP Hotel Booking or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review plugin data, recent administrative actions, logs, and affected workflows for suspicious changes or abuse attempts.
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, WooCommerce, booking/support 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 WP Hotel Booking version is version 2.3.2 or newer, and record the patched version in the remediation ticket.
Verify the vulnerable workflow no longer reproduces after the update or mitigation.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, 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

WordPress

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-11901?

WP Hotel Booking versions listed as affected should be reviewed: *-2.3.1.

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.