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

CVE-2024-35761

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 (XSS or 'Cross-site Scripting') vulnerability in vCita Online Booking & Scheduling Calendar for WordPress by vcita allows Stored XSS.This issue affects Online Booking & Scheduling Calendar for WordPress by vcita: from n/a through 4.4.0.

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

Stored XSS vulnerability in vCita Online Booking & Scheduling Calendar for WordPress plugin (versions through 4.4.0) allows attackers to inject malicious scripts through unsanitized user input that gets stored and executed when other users view the affected web pages.

MitigationUpdate the plugin to a version beyond 4.4.0 which contains the fix; if no update is available, implement proper input sanitization and output encoding on all user-supplied data 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.4.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'vcita Online Booking & Scheduling Calendar' in the installed plugins list
    Affected if The plugin appears in the installed plugins list and no version is visible
  2. Check installed plugin version
    In WordPress Admin > Plugins, click on the vcita plugin to view its details, or read the plugin header from wp-content/plugins/vcita-online-booking-scheduling-calendar/online-booking-scheduling-calendar.php to find the Version: X.X.X field
    Affected if The displayed version is 4.4.0 or lower (any version below 4.4.1)
  3. Identify active booking calendar instances
    Review pages and posts where the vcita booking calendar shortcode or widget is embedded. Common locations include appointment booking pages, contact pages, or sidebar widgets using the plugin
    Affected if The booking calendar is publicly accessible and accepting user input without known patches applied
  4. Inspect stored form data for malicious scripts
    If you have database access, examine the tables where vcita stores booking entries (look for tables prefixed with wp_vcita or similar) for unsanitized script tags in name, email, or message fields
    Affected if Database records contain raw HTML or script tags in user-submitted fields
  5. View rendered pages for injected scripts
    Visit pages containing the vcita booking calendar, right-click and view page source, or use browser developer tools to inspect the HTML for any script tags or event handlers that were not intentionally added
    Affected if Unexpected script tags, iframe elements, or JavaScript event handlers appear in the booking calendar output

You are affected if the vcita Online Booking & Scheduling Calendar plugin version is 4.4.0 or lower AND the booking calendar is active on your site, as the vulnerability requires both the vulnerable plugin version and the presence of user-accessible input fields to store malicious scripts.

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.4.1 or later
Fixed in 4.4.1
Interim mitigation

Update the plugin to a version beyond 4.4.0 which contains the fix; if no update is available, implement proper input sanitization and output encoding on all user-supplied data before rendering.

Recommended fix High confidence

vCita Online Booking & Scheduling Calendar version 4.4.1

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find the 'Online Booking & Scheduling Calendar by vcita' plugin
  4. 4. Click 'Update now' to upgrade to version 4.4.1
  5. 5. After updating, clear any site caches if applicable
  6. 6. Verify the plugin shows version 4.4.1 in the Plugins list

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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