dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-14075

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WP Hotel Booking plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.2.7. This is due to the plugin exposing the 'hotel_booking_fetch_customer_info' AJAX action to unauthenticated users without proper capability checks, relying only on a nonce for protection. This makes it possible for unauthenticated attackers to retrieve sensitive customer information including full names, addresses, phone numbers, and email addresses by providing a valid email address and a publicly accessible nonce.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Hotel Booking WordPress plugin (versions up to 2.2.7) exposes the hotel_booking_fetch_customer_info AJAX action to unauthenticated users. The endpoint relies only on a nonce for protection rather than proper capability checks, allowing attackers to retrieve customer PII (names, addresses, phone numbers, email addresses) by providing a valid email address and the publicly accessible nonce.

MitigationUpdate to the latest patched version of WP Hotel Booking plugin and ensure the AJAX action includes proper authentication and capability verification before returning customer data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WP Hotel Booking plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Hotel Booking', or check the plugin files in /wp-content/plugins/ and read the main PHP file header for the Version field
    Affected if The plugin is installed and the Version field shows 2.2.7 or lower
  2. Compare installed version to affected range
    Read the plugin version from the plugin header or version file, then compare numerically against 2.2.7 (any version 2.2.7 or lower is affected)
    Affected if Installed version is 2.2.7 or any earlier version
  3. Verify AJAX action exists
    Check the plugin source code for add_action('wp_ajax_hotel_booking_fetch_customer_info') or add_action('wp_ajax_nopriv_hotel_booking_fetch_customer_info') to confirm the vulnerable endpoint is registered
    Affected if The AJAX action 'hotel_booking_fetch_customer_info' is registered, especially with 'wp_ajax_nopriv_' prefix
  4. Confirm lack of capability check in AJAX handler
    Examine the callback function for hotel_booking_fetch_customer_info to see if it calls current_user_can() or a proper capability check before returning customer data
    Affected if The AJAX handler returns customer PII without verifying user capabilities (only relies on nonce validation)

A user is affected if WP Hotel Booking plugin version 2.2.7 or lower is installed and the hotel_booking_fetch_customer_info AJAX action is accessible to unauthenticated users without proper capability verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of WP Hotel Booking plugin and ensure the AJAX action includes proper authentication and capability verification before returning customer data.

Recommended fix Moderate confidence

WP Hotel Booking version 2.2.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Hotel Booking plugin
  4. Check if an update to version 2.2.8 or higher is available
  5. If update available, click 'Update Now' to install the patched version
  6. If no automatic update appears, manually download version 2.2.8 or later from wordpress.org/plugins/wp-hotel-booking/ and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the AJAX action 'hotel_booking_fetch_customer_info' now properly checks user capabilities

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data