CVE-2026-5513: Online Scheduling and Appointment Booking System – Bookly <= 27.2 - Unauthenticated Stored Cross-Site Scripting via 'bookly-customer-full-name' Cookie
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bookly-customer-full-name' cookie in versions up to, and including, 27.2 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. Exploitation requires 'Remember personal information in cookies' setting to be enabled (disabled by default).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Disable the 'Remember personal information in cookies' setting in the Bookly plugin to prevent storage of the 'bookly-customer-full-name' cookie that can be used for unauthenticated stored XSS. (This setting is disabled by default.)
Online Scheduling and Appointment Booking System – Bookly (WordPress plugin) Remember personal information in cookies = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5513?
The severity of CVE-2026-5513 is classified as high, with a score of 7.2.
How do I fix CVE-2026-5513?
To fix CVE-2026-5513, update the Bookly plugin to a version newer than 27.2 that addresses the stored cross-site scripting vulnerability.
What does CVE-2026-5513 affect?
CVE-2026-5513 affects the Bookly plugin for WordPress versions up to and including 27.2.
What kind of vulnerability is CVE-2026-5513?
CVE-2026-5513 is a stored cross-site scripting (XSS) vulnerability.
Who is impacted by CVE-2026-5513?
Users of the Bookly WordPress plugin who are utilizing versions up to 27.2 without input sanitization are at risk from CVE-2026-5513.