Missing AuthorizationWeakness · CWE-862

CVE-2025-68976

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Eagle-Themes Eagle Booking eagle-booking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Eagle Booking: from n/a through <= 1.3.4.3.

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

The Eagle Booking plugin <= 1.3.4.3 contains a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This allows authenticated users (or potentially unauthenticated depending on the specific flaw) to perform actions they should not have permission to access, likely through direct object references or missing permission checks on sensitive functionality.

MitigationImplement proper role-based access control (RBAC) checks on all sensitive endpoints and actions, ensuring users can only access resources and functions authorized for their privilege level.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Check the installed Eagle Booking plugin version
    Access the WordPress admin panel under Plugins > Installed Plugins and locate Eagle Booking, or inspect the main plugin file (e.g., eagle-booking.php) for a version constant or header declaring the version number
    Affected if The displayed version is 1.3.4.3 or any lower version number (e.g., 1.3.4.2, 1.3.4.1, 1.3.4.0)
  2. Identify if user authentication is enabled
    Determine whether the WordPress site has user registration enabled (Settings > General > Membership) and whether any user roles exist beyond administrator
    Affected if The site allows user registration or has non-admin user accounts present in the system
  3. Test access to sensitive plugin functions without proper authorization
    Attempt to access plugin admin pages, booking management functions, or settings endpoints while logged in as a low-privilege user (subscriber or contributor role)
    Affected if Low-privilege users can view, modify, or delete booking data, access plugin settings, or execute functions that should require administrator privileges
  4. Inspect plugin files for missing capability checks
    Review PHP files in the plugin directory for functions handling bookings, settings, or user data, looking for missing current_user_can() or role verification calls before sensitive operations
    Affected if Sensitive functions execute without verifying the current user's role or capability permissions
  5. Check for exposed AJAX endpoints
    Examine the plugin's AJAX action handlers (wp_ajax_* and wp_ajax_nopriv_* hooks) to identify endpoints that process sensitive data without authorization validation
    Affected if AJAX endpoints accept requests from unauthorized users or do not validate user permissions before processing data

A user is affected if the installed Eagle Booking plugin version is 1.3.4.3 or lower AND the site has non-admin user accounts or exposed endpoints that allow unauthorized access to booking or administrative functions.

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 access control (RBAC) checks on all sensitive endpoints and actions, ensuring users can only access resources and functions authorized for their privilege level.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68976 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68976 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