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

CVE-2024-47638

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-05
Fix available
A fix is available. Upgrade to 4.5 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in vcita Online Booking & Scheduling Calendar for WordPress by vcita meeting-scheduler-by-vcita allows Reflected XSS.This issue affects Online Booking & Scheduling Calendar for WordPress by vcita: from n/a through <= 4.4.6.

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

Reflected XSS vulnerability in vcita Online Booking & Scheduling Calendar for WordPress plugin (meeting-scheduler-by-vcita) up to version 4.4.6. User-supplied input is reflected in the web page response without proper sanitization or output encoding, allowing injection of malicious scripts that execute in victim browsers.

MitigationUpdate to the latest version of the plugin when available, or implement proper input validation and output encoding on all user-controlled parameters. As a WordPress plugin, ensure all form inputs and URL parameters are sanitized before rendering.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 vcita booking plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'meeting-scheduler-by-vcita' or containing 'vcita'. Alternatively, list installed plugins via WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder 'meeting-scheduler-by-vcita' or a vcita-related plugin exists in the WordPress installation.
  2. Determine installed plugin version
    Open the main plugin file (usually meeting-scheduler-by-vcita.php) and look for the version constant in the plugin header comment. Alternatively, check the WordPress plugin admin page which displays the version number.
    Affected if The displayed version number is 4.4.6 or lower (any version less than 4.5).
  3. Identify reflected parameters in plugin URLs
    Review the plugin's PHP source files for occurrences of $_GET, $_POST, or $_REQUEST that output to HTML without sanitization functions like esc_html(), esc_attr(), or wp_kses(). Focus on files handling front-end booking or scheduling pages.
    Affected if User-controlled parameters from $_GET/$_POST are echoed directly to HTML output without sanitization functions.
  4. Test for reflected XSS via URL parameters
    If the plugin exposes booking or scheduling pages (e.g., /?page=vcita_booking or similar), craft a test URL with a harmless script payload in a parameter (e.g., ?name=<script>alert(1)</script>) and observe if the payload appears unescaped in the page response.
    Affected if The injected script tags or event handlers render literally in the browser rather than as encoded HTML entities.

You are affected if the vcita Online Booking plugin is installed with any version below 4.5 and user-supplied input is reflected in the page output without sanitization, allowing script injection via URL parameters.

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 or later
Fixed in 4.5
Interim mitigation

Update to the latest version of the plugin when available, or implement proper input validation and output encoding on all user-controlled parameters. As a WordPress plugin, ensure all form inputs and URL parameters are sanitized before rendering.

Recommended fix High confidence

4.5

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the 'Online Booking & Scheduling Calendar by vcita' (meeting-scheduler-by-vcita) plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.5 or later
  5. 5. Alternatively, manually download version 4.5 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After upgrade, verify the plugin is running version 4.5 or higher

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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