dbcve.org
Booking CalendarWordPress extension · Wpdevart

CVE-2022-47438

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to after 3.2.3 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
Auth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in WpDevArt Booking calendar, Appointment Booking System plugin <= 3.2.3 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 confidence

Authenticated editor+ users can inject persistent malicious JavaScript into booking calendar fields. The injected script executes when other users view the affected booking pages, allowing cookie theft, session hijacking, or phishing attacks.

MitigationUpdate WpDevArt Booking calendar plugin to version >3.2.3. As an interim measure, disable the plugin until patched or restrict editor-level user accounts.

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
Booking CalendarWordPress extension
Affected:<= 3.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
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. Confirm WpDevArt Booking Calendar plugin is installed
    Log into WordPress admin panel, navigate to Plugins section, and locate WpDevArt Booking Calendar in the list of installed plugins
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WpDevArt Booking Calendar, and view the version number displayed beneath the plugin name
    Affected if Version number is 3.2.3 or lower
  3. Verify editor-level user accounts exist
    In WordPress admin, navigate to Users section and check for any user accounts with the Editor role or higher privileges
    Affected if One or more editor+ accounts exist on the site
  4. Confirm booking calendar functionality is in use
    Check if any WordPress pages or posts contain the booking calendar shortcode or widget, or if the booking calendar is configured and accessible on the site front-end
    Affected if Booking calendar fields are published and accessible to users viewing the site

User is affected if WpDevArt Booking Calendar version 3.2.3 or lower is installed and activated, and editor-level user accounts have access to the booking calendar input fields

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.

From vendor data
Upgrade available Upgrade to a release after 3.2.3
Interim mitigation

Update WpDevArt Booking calendar plugin to version >3.2.3. As an interim measure, disable the plugin until patched or restrict editor-level user accounts.

Fix this in Booking Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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