dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5919

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
The Appointment Booking and Scheduling Calendar Plugin – WP Timetics plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the update and register_routes functions in all versions up to, and including, 1.0.36. This makes it possible for unauthenticated attackers to view and modify booking details.

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 · high confidence

The WP Timetics WordPress plugin lacks capability checks on the update and register_routes API functions, allowing unauthenticated attackers to directly access these privileged endpoints. This authorization bypass enables viewing and modifying all booking data stored by the plugin without any authentication credentials.

MitigationUpdate the WP Timetics plugin to version 1.0.37 or later which contains the capability check fix. If immediate update is not possible, consider restricting access to the affected API endpoints via web server configuration or temporarily disabling the plugin.

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
None

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

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

  1. Verify WP Timetics plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the timetics folder, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%timetics%';
    Affected if The plugin folder exists or the plugin is in the active plugins list
  2. Determine the installed WP Timetics version
    Check the plugin main file header: look in wp-content/plugins/timetics/timetics.php or wp-content/plugins/timetics/index.php for the 'Version:' comment, or query: SELECT meta_value FROM wp_postmeta WHERE meta_key = 'version' AND post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'timetics');
    Affected if Version is present and is lower than 1.0.37 (the fixed version)
  3. Check if REST API endpoints are exposed
    Send a GET request to the WP Timetics REST API endpoint without authentication headers: curl -s https://yourdomain.com/wp-json/timetics/v1/appointments (or /wp-json/timetics/v1/bookings depending on the endpoint structure)
    Affected if The endpoint returns booking data or valid JSON response without requiring authentication (HTTP 200 instead of 401/403)
  4. Test unauthenticated access to update endpoints
    Send a POST request to the update endpoint without auth credentials: curl -X POST -H 'Content-Type: application/json' -d '{}' https://yourdomain.com/wp-json/timetics/v1/appointments (or the specific update endpoint path)
    Affected if The request is accepted (HTTP 200/201) rather than rejected with 401 Unauthorized or 403 Forbidden

A user is affected if the WP Timetics plugin is installed with a version earlier than 1.0.37 AND the plugin REST API endpoints are accessible without authentication credentials.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Timetics plugin to version 1.0.37 or later which contains the capability check fix. If immediate update is not possible, consider restricting access to the affected API endpoints via web server configuration or temporarily disabling the plugin.

Recommended fix High confidence

1.0.37 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Timetics plugin
  4. If the plugin shows an update available, click 'Update Now' to upgrade to version 1.0.37 or higher
  5. Alternatively, download version 1.0.37 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 1.0.37 or higher under Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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