dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62916

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in Travon WP Flights & Hotels Booking WP Plugin adiaha-hotel allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Flights & Hotels Booking WP Plugin: from n/a through <= 3.1.

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 · moderate confidence

Missing authorization vulnerability in the Travon WP Flights & Hotels Booking plugin (adiaha-hotel) allows authenticated users to access functionality beyond their privilege level due to incorrectly configured access control. The plugin fails to properly verify user permissions before executing sensitive operations, enabling privilege escalation or unauthorized access to booking management functions.

MitigationImplement proper capability checks and role-based access control (RBAC) verification on all sensitive functions and AJAX endpoints within the plugin. Use WordPress capability checks (e.g., current_user_can()) and nonce verification before performing any privileged operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Confirm the vulnerable plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Travon WP Flights & Hotels Booking' or 'adiaha-hotel' in the list of installed plugins. Note whether it is activated.
    Affected if The plugin is installed and active on the WordPress site.
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin to view its details, or inspect the plugin header in wp-content/plugins/adiaha-hotel/adiaha-hotel.php for the Version field.
    Affected if The installed version falls within any known affected version range for this CVE, or the version cannot be determined (treat as potentially vulnerable).
  3. Verify sensitive AJAX endpoints lack authorization checks
    Inspect the plugin PHP files in wp-content/plugins/adiaha-hotel/ for AJAX handlers (wp_ajax_ or wp_ajax_nopriv_ hooks). Examine if these handlers call current_user_can() or other capability checks before performing booking, user management, or configuration operations.
    Affected if AJAX endpoints that handle booking management, user data, or sensitive operations do not perform capability verification before executing.
  4. Check for exposed admin functions accessible to low-privileged users
    Review the plugin source for functions that modify bookings, create/update/delete hotel or flight data, or access user information. Test accessing these functions with a subscriber-level or contributor-level authenticated user account.
    Affected if A user with subscriber, contributor, or author role can access and execute functions intended for administrators without receiving a permission denied response.
  5. Inspect nonce verification on sensitive operations
    Search the plugin PHP files for wp_verify_nonce() or check_admin_referer() calls around sensitive operations. Determine whether these checks are missing or improperly implemented.
    Affected if Sensitive operations (booking changes, data exports, user role modifications) lack proper nonce validation, allowing CSRF-based attacks.

The site is affected if the Travon WP Flights & Hotels Booking plugin is active and authenticated users with low privileges can access booking management or admin functions 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.

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

Implement proper capability checks and role-based access control (RBAC) verification on all sensitive functions and AJAX endpoints within the plugin. Use WordPress capability checks (e.g., current_user_can()) and nonce verification before performing any privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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