dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-52801

HIGH · 7.3 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in VonStroheim TheBooking thebooking allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects TheBooking: from n/a through <= 1.4.4.

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 confidence

TheBooking plugin version 1.4.4 and below contains a missing authorization vulnerability where certain functionality is not properly constrained by Access Control Lists (ACLs). This allows unauthenticated or unauthorized users to access functions that should be restricted to specific user roles or permissions.

MitigationImplement proper role-based authorization checks (ACLs) on all sensitive functions and endpoints to ensure only authorized users can access restricted functionality. Update to version 1.4.5 or later if available.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm TheBooking plugin is installed
    Check the WordPress plugins directory or admin panel for TheBooking plugin presence
    Affected if TheBooking plugin is installed on the WordPress site
  2. Identify installed version of TheBooking
    Locate the main plugin file (e.g., thebooking.php) and read the Version header comment, or query via wp-cli: wp plugin list --name=thebooking --format=json
    Affected if Version returned is 1.4.4 or lower
  3. Compare version against affected range
    Parse the version number identified in step 2 and compare numerically to 1.4.4
    Affected if Version is 1.4.4 or any version lower (e.g., 1.4.3, 1.4.2, 1.0.0, etc.)
  4. Verify ACL protection on booking-related endpoints
    Inspect WordPress REST API routes registered by TheBooking: access /wp-json/thebooking/v1/ or check plugin file for register_rest_route calls and test unauthenticated access to sensitive endpoints
    Affected if Unauthenticated requests to booking management endpoints return successful responses instead of 401/403 errors

A site is affected if TheBooking plugin version 1.4.4 or below is installed AND unauthisticated users can access restricted booking functions without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based authorization checks (ACLs) on all sensitive functions and endpoints to ensure only authorized users can access restricted functionality. Update to version 1.4.5 or later if available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52801 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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