# CVE-2025-48916: Bookable Calendar - Less critical - Access bypass - SA-CONTRIB-2025-070

> Attackers can bypass authorization checks to access restricted calendar data via forceful browsing in the Drupal Bookable Calendar module.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2025
- **Updated:** 13 Jun 2025
- **Also known as:** DRUPAL-CONTRIB-2025-070, GHSA-p996-488q-cfm2

## What is CVE-2025-48916?

CVE-2025-48916 is a medium-severity missing authorization vulnerability in Drupal Bookable Calendar, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in Drupal Bookable Calendar allows Forceful Browsing.This issue affects Bookable Calendar: from 0.0.0 before 2.2.13.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-48916?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/bookable_calendar` | Packagist:https://packages.drupal.org/8 | All versions | 2.2.13 |

Products: Joshfabean Bookable Calendar.

## How do I fix CVE-2025-48916?

Upgrade to a fixed version.

## Is CVE-2025-48916 being exploited?

There is no known exploitation of CVE-2025-48916 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48916 and fix it if it is affected.

What it is: CVE-2025-48916 is a medium-severity missing authorization vulnerability in Drupal Bookable Calendar, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48916 in the wild and no public exploit code.

Affected product: Drupal Bookable Calendar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48916/ (Markdown: https://insights.sbomify.com/CVE-2025-48916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48916
- OSV: https://osv.dev/vulnerability/CVE-2025-48916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48916/
Summaries are generated and may contain mistakes; the official description above is the record.