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

CVE-2024-5791

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-22
Fix available
A fix is available. Upgrade to 4.4.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 Stored Cross-Site Scripting via the 'wp_id' parameter in all versions up to, and including, 4.4.2 due to missing authorization checks on processAction function, as well as insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute whenever a user accesses a wp-admin dashboard.

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 versions up to 4.4.2 contain a stored XSS vulnerability where unauthenticated attackers can inject malicious scripts via the 'wp_id' parameter. The flaw stems from missing authorization checks on the processAction function combined with insufficient input sanitization and output escaping, causing injected scripts to execute whenever users access the wp-admin dashboard.

MitigationUpdate the vcita Online Booking & Scheduling Calendar plugin to version 4.4.3 or later which includes proper authorization checks and input validation. Alternatively, temporarily restrict access to the affected endpoint until the patch can be applied.

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.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. Verify vcita plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'vcita Online Booking & Scheduling Calendar' or check the plugin files in /wp-content/plugins/ for a folder containing 'vcita' in the name
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin_plugins page, find the vcita plugin and view the version number. Alternatively, open the main plugin PHP file (usually contains 'Plugin Name: vcita') and look for the Version header in the plugin comments
    Affected if Version is less than 4.4.3 (for example: 4.4.2, 4.4.1, 4.4.0, or any version below 4.4.3)
  3. Inspect database for malicious wp_id values
    Query the WordPress options table or any vcita-related custom tables for the 'wp_id' parameter value. Run SQL: SELECT * FROM wp_options WHERE option_name LIKE '%vcita%' OR option_value LIKE '%wp_id%'; Also check POST/GET request logs for wp_id parameter submissions
    Affected if Suspicious JavaScript code (such as <script> tags, javascript: URLs, or event handlers like onload/onerror) found in wp_id stored values
  4. Check admin dashboard for injected scripts
    View the page source of the WordPress wp-admin dashboard or use browser developer tools to inspect DOM elements. Look for unexpected script tags or inline JavaScript in areas where the plugin displays data
    Affected if Malicious scripts execute or appear in the HTML source when accessing wp-admin pages, indicating successful XSS injection

The environment is affected if the vcita Online Booking & Scheduling Calendar plugin version is below 4.4.3 and malicious scripts are present in wp_id parameter values stored in the database.

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.3 or later
Fixed in 4.4.3
Interim mitigation

Update the vcita Online Booking & Scheduling Calendar plugin to version 4.4.3 or later which includes proper authorization checks and input validation. Alternatively, temporarily restrict access to the affected endpoint until the patch can be applied.

Recommended fix High confidence

Online Booking & Scheduling Calendar version 4.4.3

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate the 'Online Booking & Scheduling Calendar' plugin by vcita
  4. Click 'Update now' when version 4.4.3 is available, or manually upload version 4.4.3 from the WordPress plugin repository
  5. Verify the plugin version shows 4.4.3 or higher after updating
  6. Test that the booking and scheduling functionality works correctly after the update

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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