Online Booking \& Scheduling CalendarWordPress extension · Vcita
CVE-2024-37499
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in vCita Online Booking & Scheduling Calendar for WordPress by vcita allows Path Traversal.This issue affects Online Booking & Scheduling Calendar for WordPress by vcita: from n/a through 4.4.2.
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 confidencePath traversal vulnerability in vCita Online Booking & Scheduling Calendar for WordPress plugin allows attackers to access files outside the web root directory through manipulation of file path parameters. The CVSS 6.5 indicates network-exploitable issue with low attack complexity requiring no privileges or user interaction, but with limited confidentiality impact.
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
< 4.4.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify if the vCita plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for folders containing 'vcita' or 'online-booking' in the name, or list installed plugins via wp-cli: wp plugin list --status=active --field=nameAffected if The vCita Online Booking & Scheduling Calendar plugin is present in the WordPress installation
-
Identify the installed version of the vCita pluginIf the plugin folder is found, open the main PHP file (usually named similarly to the folder) and look for a version comment or constant near the top of the file. Alternatively, check the plugin's readme.txt file for the 'Stable tag' entryAffected if The version is below 4.4.3 (e.g., 4.4.2, 4.4.1, 4.3.x, etc.)
-
Check for file path parameters in plugin endpointsReview the plugin's PHP files for functions that handle file path parameters (e.g., readfile, file_get_contents, include, require with variables derived from $_GET, $_POST, or $_REQUEST). Look for parameters that might accept file paths like 'file', 'path', 'template', or 'ajax_call'Affected if The plugin contains file handling functions that accept unsanitized path parameters from user input
-
Inspect access logs for path traversal attemptsReview web server access logs (Apache error.log, Nginx access.log, or WAF logs) for requests to the plugin that include directory traversal patterns such as '../', '..\', or absolute paths like '/etc/passwd' targeting the vcita plugin URL endpointsAffected if Log entries show path traversal attempts targeting the vcita plugin (common patterns: ../../, ..\, absolute paths in query parameters)
-
Verify if the plugin is configured to expose booking-related AJAX endpointsCheck the plugin's admin settings page and main PHP files for registered AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) that handle file-related operations or calendar/template loadingAffected if The plugin has publicly accessible AJAX endpoints that process file path parameters without proper validation
A WordPress site is affected if the vCita Online Booking & Scheduling Calendar plugin is installed and the version is below 4.4.3, and the plugin exposes file-handling endpoints accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.4.3
Update to the latest patched version of the plugin when available. Until then, implement proper path sanitization using realpath() validation to ensure accessed paths remain within allowed directories, and consider WAF rules as temporary mitigation.
4.4.3
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Online Booking & Scheduling Calendar by vcita' plugin
- Click 'Update now' if an update is available, or manually download version 4.4.3 from the WordPress plugin repository
- Verify the plugin updated successfully to version 4.4.3
- Test the booking and scheduling functionality to ensure the update did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Online Booking \& Scheduling Calendar
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37499 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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