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

CVE-2025-67472

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 4.6.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in vcita Online Booking & Scheduling Calendar for WordPress by vcita meeting-scheduler-by-vcita allows Cross Site Request Forgery.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

Cross-Site Request Forgery (CSRF) vulnerability in the vcita Online Booking & Scheduling Calendar WordPress plugin (meeting-scheduler-by-vcita) allows attackers to trick authenticated administrators into performing unintended actions by leveraging the lack of anti-CSRF token validation on state-changing operations.

MitigationImplement WordPress nonce token validation on all admin actions and form submissions within the plugin. Add nonce checks to prevent forged requests from malicious sites executing on behalf of authenticated users.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if vcita Online Booking plugin is installed
    Navigate to WordPress admin > Plugins and locate 'vcita Online Booking & Scheduling Calendar' (also known as 'meeting-scheduler-by-vcita') in the installed plugins list
    Affected if The plugin does not appear in the installed plugins list (not affected if plugin is not installed)
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the vcita Online Booking plugin and view the version number displayed in the plugin details
    Affected if The displayed version number is less than 4.6.0 (e.g., 4.5.9, 4.5.8, etc.)
  3. Verify the plugin is active
    Confirm the vcita Online Booking plugin status shows as 'Active' in the Plugins admin page
    Affected if The plugin is active - CSRF attacks require an authenticated administrator session to exploit the missing nonce validation
  4. Confirm vulnerability scope via version comparison
    Compare your installed version against the affected range: any version below 4.6.0 contains the CSRF vulnerability due to missing anti-CSRF token validation on admin actions
    Affected if Your version is < 4.6.0 and the plugin is active - the lack of nonce validation on state-changing admin operations makes the site vulnerable to CSRF attacks

You are affected if the vcita Online Booking & Scheduling Calendar plugin (meeting-scheduler-by-vcita) is installed, active, and running a version lower than 4.6.0, as this version range lacks anti-CSRF token validation on admin actions.

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

Implement WordPress nonce token validation on all admin actions and form submissions within the plugin. Add nonce checks to prevent forged requests from malicious sites executing on behalf of authenticated users.

Recommended fix High confidence

4.6.0

  1. 1. Create a full backup of the WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the 'Online Booking & Scheduling Calendar by vcita' (meeting-scheduler-by-vcita) plugin.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.6.0.
  6. 6. Alternatively, download version 4.6.0 from the official WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 4.6.0 by checking the plugin details.
  8. 8. Test the booking and scheduling functionality to ensure the plugin works correctly after the update.
Caveat No specific breaking changes documented in available references; standard WordPress plugin update risks apply

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

Fix this in Online Booking \& Scheduling Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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