dbcve.org
Booking Ultra Pro Appointments Booking CalendarWordPress extension · Bookingultrapro

CVE-2022-46816

HIGH · 8.8 CVSS v3.1 Published 2023-05-24
Fix available
A fix is available. Upgrade to after 1.1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in Booking Ultra Pro Appointments Booking Calendar Plugin plugin <= 1.1.4 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Booking Ultra Pro WordPress plugin versions 1.1.4 and below allows attackers to trick authenticated users into executing unintended actions by leveraging the lack of proper nonce validation on sensitive operations.

MitigationUpdate the Booking Ultra Pro plugin to a version newer than 1.1.4; if no patched version exists, disable the plugin until a fix becomes available.

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 Ultra Pro Appointments Booking CalendarWordPress extension
Affected:<= 1.1.4

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Booking Ultra Pro plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the booking-ultra-pro folder
    Affected if The plugin folder exists and the plugin is active
  2. Check installed plugin version
    In WordPress admin, find Booking Ultra Pro in the plugins list and read the version number displayed beneath the plugin name; alternatively, open the main plugin PHP file and locate the 'Version' header in the plugin comments
    Affected if Version number is 1.1.4 or lower
  3. Confirm authenticated user access exists
    Check if any user accounts exist with access to WordPress admin dashboard or any role that can access Booking Ultra Pro functionality
    Affected if At least one user account can authenticate to the WordPress site where the plugin is installed

You are affected if Booking Ultra Pro plugin is installed at version 1.1.4 or below and your WordPress site has at least one authenticated user account.

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 1.1.4
Interim mitigation

Update the Booking Ultra Pro plugin to a version newer than 1.1.4; if no patched version exists, disable the plugin until a fix becomes available.

Fix this in Booking Ultra Pro Appointments Booking Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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