Appointment Booking CalendarWordPress extension · Codepeople
CVE-2025-46247
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 codepeople Appointment Booking Calendar appointment-booking-calendar allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Appointment Booking Calendar: from n/a through <= 1.3.92.
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 (broken access control) vulnerability in the Appointment Booking Calendar plugin allows unauthenticated or unauthorized users to access functionality that should be restricted by access control lists. The CVSS 9.8 indicates this is network-exploitable with no privileges required and complete impact on confidentiality, integrity, and availability.
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.93CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the Appointment Booking Calendar plugin is installedCheck your WordPress plugins directory or wp-content/plugins folder for the 'appointment-booking-calendar' directory, or look for the plugin in WordPress admin under PluginsAffected if The plugin directory or listing exists on the system
-
Identify the installed plugin versionLocate the main plugin file (typically appointment-booking-calendar.php) and open it to find the 'Version' header in the plugin comments, or check the WordPress plugin admin page for the installed version numberAffected if The version number is below 1.3.93
-
Confirm the vulnerability is present via version comparisonCompare your installed version against the affected range: any version below 1.3.93 is vulnerable to this broken access control issueAffected if Installed version is less than 1.3.93
You are affected if the Codepeople Appointment Booking Calendar plugin is installed and its version is below 1.3.93, as this version range contains the missing authorization vulnerability that allows unauthenticated or unauthorized users to access restricted functionality.
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.93
Update the Appointment Booking Calendar plugin to the latest version (beyond 1.3.92) which should contain proper authorization checks. If no update is available, implement role-based access control checks at all sensitive function entry points and verify user permissions before executing privileged operations.
1.3.93
- 1. Backup your WordPress site and database before performing any updates.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Locate 'Appointment Booking Calendar' plugin in the list.
- 4. Click 'Update now' if an update is available, or manually upload version 1.3.93 of the plugin.
- 5. Verify the update was successful by confirming the plugin version is 1.3.93 or later.
- 6. Test appointment booking functionality to ensure the plugin is working 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
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46247 — 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-2025-46247 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