dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-14352

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-07
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 Awesome Hotel Booking plugin for WordPress is vulnerable to unauthorized modification of data due to incorrect authorization in the room-single.php shortcode handler in all versions up to, and including, 1.0.3. This is due to the plugin relying solely on nonce verification without capability checks. This makes it possible for unauthenticated attackers to modify arbitrary booking records by obtaining a nonce from the public booking form.

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 Awesome Hotel Booking WordPress plugin has an incorrect authorization vulnerability in the room-single.php shortcode handler. The plugin only verifies a nonce token without performing capability checks, allowing unauthenticated attackers to modify arbitrary booking records by obtaining a nonce from the public booking form. This is an IDOR (Insecure Direct Object Reference) combined with broken access control.

MitigationUpgrade to version 1.0.4 or later which includes proper capability checks. Alternatively, add capability verification before allowing any booking modifications, ensuring the current user owns or has permission to modify the specific booking record.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Locate the Awesome Hotel Booking plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and find 'Awesome Hotel Booking', or check your wp-content/plugins directory for a folder containing 'awesome-hotel-booking' or similar naming. Note the installed version from the plugin metadata.
    Affected if Plugin is installed and version is below 1.0.4 (or version cannot be determined and the plugin appears unmaintained)
  2. Verify the vulnerable file room-single.php exists
    Check the plugin directory for the file room-single.php (typically in the main plugin folder or a shortcodes subfolder). Use file search: find /path/to/wp-content/plugins/ -name 'room-single.php' 2>/dev/null
    Affected if The file room-single.php exists in the plugin directory, indicating the vulnerable shortcode handler is present
  3. Inspect the shortcode handler for capability checks
    Open room-single.php and search for the function handling booking modifications (look for 'update_booking', 'modify_booking', 'save_booking', or similar). Check if the code contains current_user_can() or a capability check before processing booking modifications. Also verify it only checks for a nonce (wp_verifyNonce or check_ajax_referer) without a capability gate.
    Affected if The code only validates a nonce token without calling current_user_can() or equivalent capability verification before allowing booking record changes
  4. Confirm the booking modification endpoint is accessible
    Check if the shortcode [room-single] is in use on any public page (Pages > All Pages, search content for [room-single]), or if booking modification actions are hooked to WordPress actions that respond to unauthenticated requests (look for 'wp_ajax_nopriv_' or 'wp_ajax_' hooks handling bookings without capability gates).
    Affected if The booking form or room-single shortcode is exposed on a public page, allowing unauthenticated access to the vulnerable handler

You are affected if the Awesome Hotel Booking plugin is installed with a version below 1.0.4 and the room-single.php file contains a booking modification handler that only validates a nonce without verifying user capabilities.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.0.4 or later which includes proper capability checks. Alternatively, add capability verification before allowing any booking modifications, ensuring the current user owns or has permission to modify the specific booking record.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14352 — 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-14352 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