CVE-2026-92799 ladela CVE debrief

Who should care

Defenders responsible for WordPress installations using the Bookly plugin should assess exposure and prioritize verification of customer records and booking notifications. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, particularly those using the Bookly plugin. They should also review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-92799 allows unauthenticated attackers to bypass phone/email ownership verification and overwrite customer records in the Bookly plugin for WordPress. Defenders should verify exposure, assess impact, and prioritize remediation.

• Verify exposure and assess impact on customer records and booking notifications
• Implement additional security measures to prevent unauthorized access to customer data
• Update to a patched version of the Bookly plugin if necessary

Technical summary

The vulnerability is caused by the `postValidateCustomer()` function using a loose PHP inequality operator (`!=`) to compare the session-stored one-time verification code against the attacker-supplied `verification_code` parameter. This flaw is exposed by the booking AJAX controller registering all its methods as `wp_ajax_nopriv_` handlers and unconditionally overriding `csrfTokenValid()` to return true, allowing unauthenticated attackers to bypass the phone/email ownership verification step and overwrite customer records.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, particularly those using the Bookly plugin.

Recommended defensive actions

• Verify the version of the Bookly plugin and update to a patched version if necessary
• Assess the impact of this vulnerability on customer records and booking notifications
• Implement additional security measures to prevent unauthorized access to customer data
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the `postValidateCustomer()` function using a loose PHP inequality operator (`!=`) to compare the session-stored one-time verification code against the attacker-supplied `verification_code` parameter. This flaw is exposed by the booking AJAX controller registering all its methods as `wp_ajax_nopriv_` handlers and unconditionally overriding `csrfTokenValid()` to return true.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.