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

CVE-2024-5859

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 4.2.3 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
The Online Booking & Scheduling Calendar for WordPress by vcita plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘d’ parameter in all versions up to, and including, 4.4.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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

The vcita WordPress booking plugin fails to sanitize the 'd' parameter before reflecting it in the HTTP response, allowing attackers to inject arbitrary JavaScript via crafted URLs. This reflected XSS requires social engineering to trick users into clicking malicious links.

MitigationUpdate the vcita Online Booking & Scheduling Calendar plugin to version 4.4.3 or later. As an interim measure, configure a WAF to filter malicious patterns in the 'd' parameter.

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

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. Confirm vcita plugin installation
    Check WordPress plugins directory for 'vcita Online Booking' or 'vcita' plugin, or search site source for 'vcita' references
    Affected if Plugin is installed and active
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > vcita Online Booking and note the version number
    Affected if Version is present and below 4.2.3
  3. Inspect plugin files for version
    If admin access unavailable, inspect plugin directory (typically /wp-content/plugins/vcita-online-booking-scheduling-calendar/) for version in main PHP file header or readme.txt
    Affected if Version file shows version below 4.2.3
  4. Verify vulnerability presence
    Submit a test request with a benign payload in the 'd' parameter (such as ?d=test) and observe if the value is reflected unsanitized in the HTTP response
    Affected if The 'd' parameter value is reflected directly in the response without encoding or sanitization

Your environment is affected if the vcita Online Booking & Scheduling Calendar plugin is installed with a version lower than 4.2.3 and the 'd' parameter is reflected in responses without sanitization.

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.2.3 or later
Fixed in 4.2.3
Interim mitigation

Update the vcita Online Booking & Scheduling Calendar plugin to version 4.4.3 or later. As an interim measure, configure a WAF to filter malicious patterns in the 'd' parameter.

Recommended fix Moderate confidence

4.2.3 or later (note: official description references 4.4.2 as affected, so consider latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Online Booking & Scheduling Calendar' plugin by vcita
  4. Click 'Update now' if an update is available, or manually download version 4.2.3 or higher from the WordPress plugin repository
  5. Verify the updated version number after installation

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

Fix this in Online Booking \& Scheduling Calendar Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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