Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-11901Published · Updated

Action summary

Affected: ≤2.3.1Update to 2.3.2 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-345 Insufficient Verification of Data Authenticity
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WP Hotel Booking wp-hotel-booking

  1. Affected≤ 2.3.1
  2. Patched in2.3.2

Update to 2.3.2 or newer.

You are affected if you run ≤ 2.3.1. Version 2.3.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP Hotel Booking.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.3.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP Hotel Booking to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to valent1.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP Hotel Booking

All 28
More vulnerabilities in WP Hotel Booking
SeverityVulnerabilityCVEPublished
Medium6.5Authenticated (Custom role+) SQL Injection
<2.3.2Update to 2.3.2
CVE-2026-15153
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'widget_search' Shortcode Attribute
≤2.3.2Update to 2.3.3
CVE-2026-15464
Medium5.3Unauthenticated Price Manipulation
≤2.3.2Update to 2.3.3
CVE-2026-15149
Medium6.1Reflected Cross-Site Scripting via 'check_in_date' Parameter
≤2.3.2Update to 2.3.3
CVE-2026-15094
Medium6.1Reflected Cross-Site Scripting via 'check_in_date' and 'check_out_date' Parameters
≤2.3.1Update to 2.3.2
CVE-2026-11392

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?