dbcve.org
Online Booking \& Scheduling CalendarWordPress extension · Vcita

CVE-2025-67559

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 4.6.0 or later.
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 vcita Online Booking & Scheduling Calendar for WordPress by vcita meeting-scheduler-by-vcita allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Online Booking & Scheduling Calendar for WordPress by vcita: from n/a through <= 4.5.5.

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 vcita Online Booking & Scheduling Calendar plugin for WordPress contains a missing authorization vulnerability (CWE-862) where certain functions or API endpoints lack proper access control checks. This allows unauthenticated or low-privilege attackers to potentially access booking management features that should require elevated privileges, due to incorrectly configured access control security levels.

MitigationUpdate the vcita Online Booking & Scheduling Calendar plugin to the latest version which should include proper authorization controls, or implement server-side access control validation at the web application firewall level as a temporary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Booking \& Scheduling CalendarWordPress extension
Affected:< 4.6.0

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. Verify vcita plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'vcita Online Booking & Scheduling Calendar' in the list
    Affected if The vcita Online Booking & Scheduling Calendar plugin is present and active on the WordPress site
  2. Check installed plugin version
    In the Plugins list, click on the plugin details or view the plugin files to find the version number in the main plugin file header (usually plugin-name.php)
    Affected if The installed version is lower than 4.6.0 (e.g., 4.5.x, 4.4.x, etc.)
  3. Identify exposed API endpoints
    Review the plugin directory (wp-content/plugins/vcita-online-booking-scheduling-calendar) for REST API routes or AJAX handlers that handle booking management functions by examining the includes folder and main plugin file
    Affected if API endpoints related to booking management (appointments, clients, schedules) are registered without capability checks or nonce verification for authorization
  4. Test unauthenticated access to booking features
    Attempt to access common booking management paths such as /wp-json/vcita/, /wp-admin/admin-ajax.php?action=vcita_*, or direct PHP files in the plugin directory without logging in
    Affected if The server returns booking data, accepts booking modifications, or allows client management operations without requiring authentication or elevated privileges

A site is affected if it has the vcita Online Booking & Scheduling Calendar plugin installed with a version lower than 4.6.0 and has accessible booking management endpoints that do not require proper 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
Upgrade available Upgrade to 4.6.0 or later
Fixed in 4.6.0
Interim mitigation

Update the vcita Online Booking & Scheduling Calendar plugin to the latest version which should include proper authorization controls, or implement server-side access control validation at the web application firewall level as a temporary measure.

Recommended fix High confidence

4.6.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Online Booking & Scheduling Calendar by vcita' plugin
  4. Check if the current version is below 4.6.0
  5. If update available, click 'Update Now' to upgrade to version 4.6.0
  6. Alternatively, download version 4.6.0 from the WordPress plugin repository or vcita website
  7. Deactivate and delete the old plugin version if automatic update doesn't work, then upload and install version 4.6.0
  8. Verify the plugin is running at version 4.6.0 after update

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

Fix this in Online Booking \& Scheduling Calendar 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 the upgrade done

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