Bookable CalendarDrupal extension · Joshfabean
CVE-2025-48916
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 Drupal Bookable Calendar allows Forceful Browsing.This issue affects Bookable Calendar: from 0.0.0 before 2.2.13.
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 confidenceMissing authorization check in Drupal Bookable Calendar module allows authenticated users to perform forced browsing, accessing administrative or restricted calendar resources they should not have permission to view. This is a broken access control vulnerability where the application fails to verify user authorization before granting access to certain pages or operations.
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
Bookable CalendarDrupal extension
< 2.2.13CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Verify Bookable Calendar module is installedCheck if the Bookable Calendar module is present in your Drupal installation. In the Drupal admin UI, navigate to Extend (admin/modules) and search for 'Bookable Calendar', or run 'drush pm:list --status=enabled' and look for the module.Affected if The Bookable Calendar module is listed as installed or enabled.
-
Check installed version of Bookable CalendarFind the version number of the Bookable Calendar module. If using Drush, run 'drush pm:list | grep bookable'. Alternatively, locate the module directory (usually in modules/contrib/bookable_calendar) and check the bookable_calendar.info.yml file for the 'version' or 'core_version' entry.Affected if The installed version is lower than 2.2.13.
-
Confirm module is enabled and in useVerify the module is not just installed but actually enabled. In Drupal admin, go to Extend and ensure the checkbox next to Bookable Calendar is checked, or run 'drush state-get system.module' to check if bookable_calendar is listed as enabled.Affected if The module shows as enabled in Drupal's module management.
-
Audit user roles with calendar access permissionsReview which authenticated roles have permissions related to Bookable Calendar. Navigate to People > Roles (admin/people/roles) and for each role check the permissions at People > Permissions (admin/people/permissions) for any 'bookable calendar' or 'calendar' related permissions. Focus on roles that have access to administrative or booking features.Affected if Authenticated users (not just administrators) have permissions to view, edit, or manage calendar resources.
-
Test for unauthorized access to restricted calendar pagesUsing a non-administrator authenticated account (or via browser inspection of permissions), attempt to directly access known administrative calendar paths such as admin/config/bookable-calendar, admin/content/bookable-calendar, or any calendar resource URLs that should be restricted to administrators. Note which URLs return content versus access denied.Affected if A non-administrator authenticated user can access pages or resources intended only for administrative roles.
You are affected if the Bookable Calendar module is installed with a version lower than 2.2.13 and authenticated users can access administrative or restricted calendar resources without proper authorization checks.
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 · scoped2.2.13
Update Bookable Calendar to version 2.2.13 or later to receive the authorization fix. Review user role permissions and access control configurations as part of remediation.
2.2.13
- 1. Backup your Drupal site database and files before making any changes
- 2. Update the Bookable Calendar module using Composer: run 'composer update drupal/bookable_calendar' or use your site's update mechanism
- 3. Alternatively, navigate to Extend > Check for updates in the Drupal admin UI and update Bookable Calendar to version 2.2.13
- 4. Clear Drupal caches after the update by running 'drush cr' or via the admin UI at Configuration > Development > Performance > Clear all caches
- 5. Verify the update was successful by checking the module version at Extend > Bookable Calendar
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bookable Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.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-2025-48916 — 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-48916 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