dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64261

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-13
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 codepeople Appointment Booking Calendar appointment-booking-calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Appointment Booking Calendar: from n/a through <= 1.3.95.

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

The Appointment Booking Calendar plugin for WordPress has a missing authorization vulnerability where certain functionality can be accessed without proper access control checks due to incorrectly configured security levels. An attacker could potentially exploit this to access administrative functions or sensitive data without proper authentication or authorization.

MitigationImplement proper capability checks and authorization verification for all sensitive operations in the plugin, ensuring that user permissions are validated before executing any privileged actions.

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. Identify if the Appointment Booking Calendar plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'appointment-booking-calendar' or similar naming. Alternatively, search the WordPress admin plugins list for 'Appointment Booking Calendar' or its alternate names like 'appointment-calendar' or 'abc'
    Affected if The plugin folder or entry exists in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically plugin-name.php in the plugin folder) and locate the version comment in the file header, or check the readme.txt file for the 'Stable tag' version number
    Affected if The installed version matches or falls within any affected version range (compare against publicly disclosed vulnerable versions if available)
  3. Check for exposed administrative endpoints or AJAX actions
    Review the plugin's PHP files for registered WordPress hooks (add_action, add_filter) that handle admin functionality. Specifically look for AJAX handlers (wp_ajax_*) or admin pages that may lack capability checks (current_user_can)
    Affected if The plugin registers administrative actions or pages without verifying user capabilities using current_user_can() or similar authorization functions
  4. Verify authorization on sensitive plugin functions
    Use a WordPress user role inspector or manually examine plugin source code for functions handling booking management, customer data, or settings. Search for function calls that modify data or access sensitive information without capability validation
    Affected if Sensitive operations can be executed by unauthenticated users or users lacking administrative privileges
  5. Test external accessibility of vulnerable functionality
    If the plugin exposes REST API endpoints or direct PHP files in the wp-content/plugins directory, attempt to access them without authentication or with a low-privilege user account to confirm if authorization is enforced
    Affected if Administrative functions, booking data, or settings are accessible without proper authentication or authorization checks

The environment is affected if the Appointment Booking Calendar plugin is installed AND it exposes administrative or sensitive functionality without requiring proper WordPress capability verification (current_user_can checks) or authentication.

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 authorization verification for all sensitive operations in the plugin, ensuring that user permissions are validated before executing any privileged actions.

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-64261 — 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-64261 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