CVE-2026-5513 HIGH

CVE-2026-5513: Online Scheduling and Appointment Booking System – Bookly <= 27.2 - Unauthenticated Stored Cross-Site Scripting via 'bookly-customer-full-name' Cookie

Vendor Ladela
Product Online Scheduling and Appointment Booking System – Bookly
Weakness CWE-79 · XSS
Published June 13, 2026
Last update June 15, 2026

CVSS base score

7.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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).

Explanation of Vulnerability in Simple Terms

02Summary

Bookly versions 27.2 and earlier contain a cross-site scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious scripts into the application. The vulnerability affects the scope beyond the vulnerable component itself. An attacker can craft a malicious request to inject JavaScript that executes in users' browsers, potentially stealing session data or performing actions on their behalf.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in users' browsers and steals data or performs actions on their behalf.

Potential impact on your site

04Site Impact

Site visitors may have their sessions compromised or be tricked into performing unwanted actions without their knowledge.

Conditions required to exploit

05Prerequisites

No authentication or user interaction required; attacker can exploit this remotely by crafting a malicious request.

Key dates

06Disclosure timeline

June 13, 2026 CVE published
June 15, 2026 Record updated