dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67970

MEDIUM · 5.9 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 vertim Schedula schedula-smart-appointment-booking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Schedula: from n/a through <= 1.0.

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

Missing authorization vulnerability in the Schedula smart appointment booking plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to resources or functionality beyond the user's intended privileges.

MitigationImplement proper role-based authorization checks on all sensitive endpoints and functions, ensuring each request validates the caller's permissions before granting access to protected resources.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Confirm Schedula plugin installation and version
    Access the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'Schedula Smart Appointment Booking' and record the installed version number. Alternatively, check the plugin file header in wp-content/plugins/schedula/ for the Version field.
    Affected if The installed version exists and is within any affected version range for CVE-2025-67970 (compare your version to the official advisory for specific ranges).
  2. Identify accessible booking endpoints
    Review the Schedula plugin for publicly accessible AJAX actions or REST API endpoints. Check the main plugin PHP file for registered hooks using add_action('wp_ajax_*') or add_action('wp_ajax_nopriv_*') that handle appointment data, user data, or admin functions. Use a browser or curl to test these endpoints without authentication.
    Affected if Sensitive endpoints such as those retrieving user data, modifying appointments, or accessing admin functions are accessible to unauthenticated users (no login required).
  3. Verify authorization checks on sensitive functions
    Inspect the Schedula plugin PHP source code, specifically functions that handle appointment creation, modification, deletion, or user data retrieval. Search for current_user_can(), check_admin_referer(), or similar authorization verification calls before executing sensitive operations.
    Affected if No authorization checks (or weak/missing checks) are found before executing functions that modify or expose appointment or user data.
  4. Examine user role capability configuration
    Check the plugin settings in the WordPress admin under the Schedula plugin menu. Look for any options controlling access levels, permission settings, or role-based access controls. Also inspect the plugin code for capability definitions used when registering menu pages or protected actions.
    Affected if The plugin allows configuration of access controls that can be set too permissively, or if no capability checks are enforced on admin menu items or protected functions.

A user is affected if the Schedula plugin is installed with a version impacted by CVE-2025-679679 and sensitive endpoints or functions are accessible without proper authorization verification.

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 on all sensitive endpoints and functions, ensuring each request validates the caller's permissions before granting access to protected resources.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,700
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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