Online Booking \& Scheduling CalendarWordPress extension · Vcita
CVE-2023-39992
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in vCita.Com Online Booking & Scheduling Calendar for WordPress by vcita plugin <= 4.3.2 versions.
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 confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the vCita WordPress plugin (versions 4.3.2 and below). Attackers can inject malicious JavaScript through unsanitized input parameters, which is then reflected back to the victim in the server response.
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.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm vCita plugin is installedIn WordPress admin, go to Plugins and locate the vCita Online Booking & Scheduling Calendar plugin in the listAffected if The plugin appears in the installed plugins list
-
Check the installed version numberIn the plugins list, note the version number displayed next to the vCita plugin nameAffected if Version is 4.3.2 or any version below 4.3.3 (e.g., 4.3.1, 4.3.0, etc.)
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the vCita plugin shows as Active (not deactivated)Affected if Plugin is enabled and running on the site
-
Identify user input pointsReview the plugin settings pages and any frontend booking/contact forms created by the plugin for parameters that accept user input and display it backAffected if The plugin accepts and reflects user-supplied input in its response
If the vCita Online Booking & Scheduling Calendar plugin is installed, active, and running version 4.3.2 or below, the environment is affected by this reflected XSS vulnerability.
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.3.3
Update the vCita Online Booking & Scheduling Calendar plugin to the latest version (currently unknown, but greater than 4.3.2). If no patch is available, consider disabling the plugin until a fix is released.
4.3.3
- Create a complete backup of your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find the 'Online Booking & Scheduling Calendar by vcita' plugin
- Click 'Update now' if an update is available, or manually update to version 4.3.3 or higher
- Verify the plugin version shows 4.3.3 or later after updating
- Test that the plugin functionality works correctly on your site
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
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39992 — 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-2023-39992 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