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

CVE-2025-54677

HIGH · 7.2 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 4.5.5 or later.
See remediation →
78/100
Remediation priority · High
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
Unrestricted Upload of File with Dangerous Type vulnerability in vcita Online Booking & Scheduling Calendar for WordPress by vcita meeting-scheduler-by-vcita allows Using Malicious Files.This issue affects Online Booking & Scheduling Calendar for WordPress by vcita: from n/a through <= 4.5.3.

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

Unrestricted file upload vulnerability in the vcita Online Booking & Scheduling Calendar WordPress plugin (meeting-scheduler-by-vcita) allows authenticated attackers to upload malicious file types due to insufficient validation of uploaded files, potentially leading to remote code execution.

MitigationUpdate the plugin to the latest patched version. If no patch is available, implement server-side file type validation, restrict upload directories, and disable script execution in upload directories.

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.5.5

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

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

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 vcita plugin is installed
    Navigate to WordPress admin > Plugins and look for 'vcita Online Booking & Scheduling Calendar' or 'meeting-scheduler-by-vcita' in the installed plugins list
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the vcita plugin to view version details, or inspect the plugin header in wp-content/plugins/meeting-scheduler-by-vcita/main.php for the Version field
    Affected if The installed version is below 4.5.5 (e.g., 4.5.4, 4.5.3, etc.)
  3. Verify file upload capability is accessible
    Check if the booking/calendar widget or scheduling feature includes a file attachment/upload input for appointments or client uploads
    Affected if The plugin exposes any file upload functionality to authenticated users or visitors
  4. Inspect upload directory configuration
    Check the wp-content/uploads directory and any vcita-specific subdirectories for .htaccess or configuration files that should prevent script execution
    Affected if Upload directories allow execution of uploaded files (no restrictions on .php, .phtml, .exe extensions)
  5. Confirm user authentication requirements
    Review the booking form or client portal to determine whether uploading requires authenticated user access versus public anonymous access
    Affected if The file upload feature is exposed to authenticated users (subscriber, customer, or client-level accounts) without additional validation

You are affected if the vcita Online Booking & Scheduling Calendar plugin is installed with a version lower than 4.5.5 and the file upload functionality is accessible to authenticated users.

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.5.5 or later
Fixed in 4.5.5
Interim mitigation

Update the plugin to the latest patched version. If no patch is available, implement server-side file type validation, restrict upload directories, and disable script execution in upload directories.

Recommended fix High confidence

4.5.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Online Booking & Scheduling Calendar by vcita' (meeting-scheduler-by-vcita)
  4. 4. Click 'Update now' if an update is available, or manually upload version 4.5.5 or later from the WordPress plugin repository
  5. 5. Verify the update was successful and the plugin is functioning normally

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

Fix this in Online Booking \& Scheduling Calendar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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