Appointment Booking CalendarWordPress extension · Codepeople
CVE-2022-43482
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 · uneditedMissing Authorization vulnerability in Appointment Booking Calendar plugin <= 1.3.69 on WordPress.
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 confidenceMissing Authorization vulnerability in the Appointment Booking Calendar WordPress plugin versions 1.3.69 and below allows unauthenticated or unauthorized users to access certain functions or data that should require proper capability checks or authentication.
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
Appointment Booking CalendarWordPress extension
< 1.3.70CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Appointment Booking Calendar plugin is installedLog in to WordPress admin panel, go to Plugins > Installed Plugins, and search for 'Appointment Booking Calendar' or 'Codepeople Appointment Booking Calendar' in the listAffected if plugin is not present in the installed plugins list (not vulnerable)
-
Determine the installed plugin versionIn the Plugins list, locate the Appointment Booking Calendar entry and note the version number displayed beneath the plugin name. Alternatively, access the main plugin file (usually cpabc_appointment_calendar.php) and read the 'Version:' header commentAffected if version number cannot be determined but plugin is present
-
Compare version against affected rangeCompare your installed version to the affected range: versions below 1.3.70 (1.3.69 and lower) are vulnerableAffected if installed version is 1.3.69 or lower
Your environment is affected if the Appointment Booking Calendar plugin is installed with version 1.3.69 or below, as these versions lack proper authorization checks and allow unauthorized access to certain functions.
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 · scoped1.3.70
Update the Appointment Booking Calendar plugin to the latest version which includes proper authorization checks. If updates are not immediately possible, audit the plugin code for unprotected AJAX actions or admin pages and restrict access using current_user_can() capability checks.
Appointment Booking Calendar version 1.3.70
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find 'Appointment Booking Calendar' in the plugin list
- Click 'Update now' if an update is available, or manually download version 1.3.70 or later from the WordPress plugin repository
- Verify the plugin updated successfully to version 1.3.70 or higher
- Test that the booking functionality continues to work correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Appointment Booking Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43482 — 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-2022-43482 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