dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-1920

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 Booking Calendar for Appointments and Service Businesses – Booktics plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'Extension_Controller::update_item_permissions_check' function in all versions up to, and including, 1.0.16. This makes it possible for unauthenticated attackers to install addon plugins.

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 Booktics WordPress plugin lacks a capability check on the Extension_Controller::update_item_permissions_check function, allowing unauthenticated attackers to install addon plugins via this insecure direct object reference. This enables remote attackers to potentially compromise the site by adding malicious or unwanted plugins without any authentication.

MitigationUpdate the Booktics plugin to version 1.0.17 or later which includes the missing capability check. If immediate update is not possible, consider disabling the plugin or restricting access to the affected endpoint at the web server 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Locate the Booktics plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'booktics' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for Booktics.
    Affected if The Booktics plugin is not found in the plugins directory or is not listed in WordPress admin, then this CVE does not apply.
  2. Identify the installed Booktics version
    If the plugin is installed, open the main plugin file (usually booktics.php) in the plugin folder and look for the 'Version' header comment at the top of the file. Alternatively, check the version displayed in WordPress admin under Plugins > Installed Plugins next to the Booktics plugin name.
    Affected if The installed version is unknown or cannot be determined from the plugin files.
  3. Compare the version against the fixed release
    Compare the identified version number to version 1.0.17. Versions prior to 1.0.17 are affected; version 1.0.17 and later include the capability check fix.
    Affected if The installed version is below 1.0.17 (for example, 1.0.16, 1.0.15, etc.), indicating the missing capability check is present.
  4. Verify the vulnerable endpoint exists
    Inspect the plugin files for the Extension_Controller class, specifically the update_item_permissions_check method. This file is typically located in includes/controllers/ or similar within the Booktics plugin folder. Check if this function is missing a capability check (such as 'manage_options' or 'install_plugins').
    Affected if The update_item_permissions_check function exists but lacks a current_user_can() or similar permission check before allowing addon plugin installation.

You are affected if the Booktics plugin is installed and the installed version is below 1.0.17, or if the Extension_Controller::update_item_permissions_check function is missing a capability 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.

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

Update the Booktics plugin to version 1.0.17 or later which includes the missing capability check. If immediate update is not possible, consider disabling the plugin or restricting access to the affected endpoint at the web server level.

Recommended fix Moderate confidence

Version 1.0.17 or later

  1. Update the Booktics plugin to the latest available version from the WordPress plugin repository

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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