CVE-2026-5513
Deferred Deferred - Pending Action

Stored XSS in Bookly WordPress Plugin

Vulnerability report for CVE-2026-5513, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-13

Last updated on: 2026-06-15

Assigner: Wordfence

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-13
Last Modified
2026-06-15
Generated
2026-07-03
AI Q&A
2026-06-14
EPSS Evaluated
2026-07-02
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
bookly bookly to 27.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Detection Guidance

This vulnerability involves the 'bookly-customer-full-name' cookie being used to inject stored cross-site scripting payloads. Detection involves checking for suspicious or unexpected script content within this specific cookie.

You can inspect HTTP requests and responses to identify if the 'bookly-customer-full-name' cookie contains any malicious script tags or unusual characters.

A simple command to check for the presence of this cookie in HTTP traffic using tcpdump or tshark might be:

  • tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'bookly-customer-full-name'

Alternatively, if you have access to the web server logs, you can search for occurrences of the 'bookly-customer-full-name' cookie and analyze its values for suspicious script content.

For example, using grep on Apache or Nginx logs:

  • grep 'bookly-customer-full-name' /var/log/apache2/access.log | grep -i '<script>'

Note that exploitation requires the 'Remember personal information in cookies' setting to be enabled in the plugin, which is disabled by default.

Impact Analysis

This vulnerability can allow unauthenticated attackers to execute arbitrary scripts in the context of the affected website. This can lead to theft of user data, session hijacking, defacement of the website, or other malicious actions performed on behalf of the user.

Because the vulnerability is a Stored Cross-Site Scripting issue, the malicious script persists and affects any user who visits the injected page, potentially compromising multiple users.

Mitigation Strategies

To mitigate this vulnerability, ensure that the 'Remember personal information in cookies' setting is disabled, as it is disabled by default and required for exploitation.

Additionally, update the Bookly plugin for WordPress to a version later than 27.2 where this vulnerability is fixed.

Executive Summary

The vulnerability exists in the Online Scheduling and Appointment Booking System – Bookly plugin for WordPress, specifically in versions up to and including 27.2. It is a Stored Cross-Site Scripting (XSS) vulnerability that occurs via the 'bookly-customer-full-name' cookie. This happens because the plugin does not properly sanitize input or escape output, allowing attackers to inject malicious web scripts.

When exploited, these injected scripts execute whenever a user accesses a page containing the malicious code. The attack requires the 'Remember personal information in cookies' setting to be enabled, which is disabled by default.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-5513. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart