dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66105

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-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
Missing Authorization vulnerability in Magepeople inc. Bus Ticket Booking with Seat Reservation allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Bus Ticket Booking with Seat Reservation: from n/a before 5.6.8.

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

This is a Missing Authorization (broken access control) vulnerability in the Magepeople Bus Ticket Booking with Seat Reservation WordPress plugin. The vulnerability allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthenticated or unauthorized access to sensitive booking functions, seat reservation data, or administrative operations that should require proper authorization checks.

MitigationImplement proper authorization checks on all sensitive endpoints and functions within the plugin, ensuring that users can only access resources and actions they are explicitly permitted to access. Update to version 5.6.8 or later if a patched version is available.

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. Verify the Magepeople Bus Ticket Booking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Magepeople Bus Ticket Booking with Seat Reservation' or check the plugins directory for the plugin files
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    Check the plugin header in the main plugin file (typically in wp-content/plugins/mage-bus-ticket-booking-with-seat-reservation/) or view the version listed in the WordPress plugins page
    Affected if The installed version is lower than 5.6.8 (the patched version)
  3. Check for exposed AJAX or REST API endpoints
    Examine the plugin code for wp_ajax and wp_ajax_nopriv hooks, and check if sensitive functions (booking management, seat reservation, admin operations) are registered with nopriv capability allowing unauthenticated access
    Affected if AJAX or API endpoints handling bookings, seat data, or admin functions are accessible to unauthenticated users (hooks with nopriv or missing capability checks)
  4. Test access to booking-related URLs
    Attempt to access common booking endpoints (such as /wp-admin/admin-ajax.php?action=mage_booking_*, /?action=mage_booking_*, or any custom REST routes) without authentication
    Affected if Sensitive booking operations, seat reservation data, or administrative functions return valid responses without requiring login
  5. Inspect capability and permission checks in plugin code
    Review the plugin source code for functions that handle bookings, reservations, or admin operations and verify if they include current_user_can() or similar authorization checks before executing sensitive actions
    Affected if Critical functions lack proper authorization checks or use weak/inadequate permission verification

A user is affected if the Magepeople Bus Ticket Booking plugin versions below 5.6.8 are installed and sensitive booking, seat reservation, or admin functions are accessible without authentication due to missing or inadequate authorization checks.

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

Implement proper authorization checks on all sensitive endpoints and functions within the plugin, ensuring that users can only access resources and actions they are explicitly permitted to access. Update to version 5.6.8 or later if a patched version is available.

Recommended fix Moderate confidence

5.6.8

  1. Backup your WordPress site before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate 'Bus Ticket Booking with Seat Reservation' by Magepeople
  5. Click 'Update Now' to install version 5.6.8
  6. Verify the update was successful by confirming the version number
  7. Test the booking functionality to ensure the plugin is working correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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