dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67574

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
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 wpdevart Booking calendar, Appointment Booking System booking-calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking calendar, Appointment Booking System: from n/a through <= 3.2.30.

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 wpdevart Booking Calendar plugin for WordPress has a missing authorization vulnerability (CWE-862) that allows attackers to access functionality they shouldn't be able to access due to incorrectly configured access control security levels. The vulnerability affects versions up to and including 3.2.30, and can be exploited without any authentication privileges.

MitigationImplement proper authorization checks on all sensitive operations and endpoints within the booking calendar system. Update to a patched version if available, or add role-based access control (RBAC) checks to verify user permissions before executing 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
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 wpdevart Booking Calendar plugin is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'booking-calendar' or search for 'wpdevart' in the plugins list via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin appears in your WordPress installation's plugin list
  2. Identify the installed plugin version
    Open the plugin's main PHP file (usually wp-content/plugins/booking-calendar/wpdevart_booking.php) and look for a version comment or check the plugin's readme.txt file for the 'Stable tag' version
    Affected if The version listed is 3.2.30 or lower (any version up to and including 3.2.30)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the wpdevart Booking Calendar status shows as 'Active'
    Affected if The plugin is enabled and running on your WordPress site
  4. Test for unauthenticated access to plugin endpoints
    Send a direct request to common plugin AJAX handlers (such as /wp-admin/admin-ajax.php?action=booking_calendar...) without providing any authentication cookies or credentials; inspect whether the server returns meaningful data or performs actions instead of rejecting the request with an authorization error
    Affected if The plugin processes requests and returns data without requiring login (HTTP 200 response with calendar data or booking operations instead of a login redirect or auth error)
  5. Review plugin user capability settings
    Check the plugin settings under Booking Calendar > Settings > General to see if 'User role for using the plugin' is set to 'Everyone' or a role that unauthenticated visitors would have, or inspect the plugin's PHP code for missing current_user_can() checks before sensitive operations
    Affected if The plugin allows unauthenticated users to access booking management features or the capability requirement is set too loosely

You are affected if the wpdevart Booking Calendar plugin versions 3.2.30 or lower is installed and active on your WordPress site, and its functionality is accessible without any user login or 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.

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

Implement proper authorization checks on all sensitive operations and endpoints within the booking calendar system. Update to a patched version if available, or add role-based access control (RBAC) checks to verify user permissions before executing privileged actions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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