CVE-2026-13424: Online Scheduling and Appointment Booking System <= 27.7 - Unauthenticated Stored Cross-Site Scripting via bookly_speed_up_update_addons AJAX action
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via booklyspeedupupdateaddons AJAX action in all versions up to, and including, 27.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injection point is the booklyspeedupupdateaddons AJAX action, which is registered as wpajaxnopriv and therefore reachable without authentication; the payload is stored verbatim in the booklylog.details column when a request is submitted without a valid signature, and executes when an administrator later views the Diagnostics → Logs page.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-13424?
The severity of CVE-2026-13424 is classified as high with a score of 7.2.
How can I mitigate CVE-2026-13424?
To mitigate CVE-2026-13424, update the Online Scheduling and Appointment Booking System Bookly plugin to the latest version beyond 27.7.
What type of vulnerability is CVE-2026-13424?
CVE-2026-13424 is a Stored Cross-Site Scripting (XSS) vulnerability.
What causes CVE-2026-13424?
CVE-2026-13424 is caused by insufficient input sanitization and output escaping in the Bookly plugin.
Who is affected by CVE-2026-13424?
Anyone using the Online Scheduling and Appointment Booking System Bookly plugin for WordPress up to version 27.7 is affected by CVE-2026-13424.