Categories
CVE-2026-92619 high CVSS 7.2

Privilege Escalation in Booking Calendar (WordPress plugin) (CVE-2026-92619)

Summary

Vulnerability in Booking Calendar (WordPress plugin) (CVE-2026-92619). Successful exploitation can lead to full system takeover. Exploitable via wpbc_ajax_option_save.

Original description

The description as published by the source.

The Booking Calendar plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 11.8.2 via the wpbc_ajax_option_save AJAX action. The vulnerability exists because the handle_ajax_save() function applies per-option safeguards only to names explicitly registered via register_option_policy(), causing get_option_policy() to return an empty policy — bypassing all can_save, force_mode, and allowed_keys checks — for any unregistered option name, including core WordPress options, while an attacker-controlled data_name parameter passes through sanitize_key() and is written directly to update_option() without restriction. This makes it possible for authenticated attackers with Editor-level access and above to escalate their privileges to Administrator by writing core WordPress options such as default_role=administrator and users_can_register=1, then self-registering a new Administrator account. The nonce check does not meaningfully restrict this attack, as both the nonce value and nonce action are attacker-supplied POST parameters, and a valid nonce is trivially obtainable via admin-ajax.php?action=rest-nonce.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-92619 has been found in Booking Calendar (WordPress plugin).
Attackers can target a specific entry point like wpbc_ajax_option_save over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Booking Calendar (WordPress plugin) CVE-2026-92619" on the vendor's site.

CVE-2026-92619 (Booking Calendar (WordPress plugin)) — CWE-269 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: wpbc_ajax_option_save / data_name
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in Booking Calendar (WordPress plugin). Attackers reach the vulnerable code path via wpbc_ajax_option_save.

📍 Affected scope

Check the vendor advisory for the affected versions of Booking Calendar (WordPress plugin). Attack surface: wpbc_ajax_option_save / data_name.

🔥 Severity

Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Booking Calendar (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details