CVE-2026-57746
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 · uneditedSubscriber Broken Access Control in Booked <= 3.0.0 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 confidenceThis is a Broken Access Control vulnerability in the Booked appointment scheduling software affecting versions 3.0.0 and below. The 'Subscriber' user role can access resources or perform actions outside their intended permissions, likely allowing privilege escalation to access administrative functions or other users' data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify the installed Booked versionLocate the version file or check the software's About/Status page, typically found in the application footer, admin dashboard, or configuration files (e.g., version.php, config.php, or a version.txt in the installation directory)Affected if The version is 3.0.0 or lower
-
Verify the Subscriber role existsAccess the user role management section in the Booked admin panel (usually under Settings > Users or Permissions) and confirm the Subscriber role is defined and enabledAffected if The Subscriber role is present and active in the system
-
Check Subscriber role permission boundariesReview the permission matrix for the Subscriber role in the admin panel to determine if it has been granted access beyond standard user capabilities (e.g., administrative functions, other users' appointments, or configuration settings)Affected if Subscriber role permissions extend beyond typical user-level access or include administrative privileges
-
Test access to administrative functionsLog in with a Subscriber-level account and attempt to access administrative paths or features (e.g., /admin, /reports, user management, or other elevated functions)Affected if A Subscriber account can access or execute administrative functions it should not be authorized to use
-
Inspect user data access isolationUsing a Subscriber account, attempt to view, modify, or delete appointments or data belonging to other usersAffected if Subscriber users can access or modify other users' appointments or personal data
You are affected if Booked version is 3.0.0 or below AND the Subscriber role has excessive permissions allowing access to administrative features or other users' data.
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.
From vendor dataUpgrade Booked to the latest version (above 3.0.0) which should contain the access control fix. If upgrading is not immediately possible, review user role permissions and implement temporary application-layer access controls.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57746 — 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-2026-57746 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